public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
* [Bug libstdc++/64443] New std::string implementation breaks tests on AArch64. [not found] <bug-64443-4@http.gcc.gnu.org/bugzilla/> @ 2014-12-30 17:10 ` belagod at gcc dot gnu.org 2014-12-31 10:31 ` belagod at gcc dot gnu.org ` (4 subsequent siblings) 5 siblings, 0 replies; 6+ messages in thread From: belagod at gcc dot gnu.org @ 2014-12-30 17:10 UTC (permalink / raw) To: gcc-bugs https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64443 --- Comment #3 from Tejas Belagod <belagod at gcc dot gnu.org> --- (In reply to Andrew Pinski from comment #1) > >This commit seems to be breaking libstdc++-v3 runs on AArch64. > > Is this under Linux or with newlib? newlib. When run on a fast-model(simulator) they fail by raising an exception. I'll post more info on the kind of exception rasied when I've investigated a bit more... ^ permalink raw reply [flat|nested] 6+ messages in thread
* [Bug libstdc++/64443] New std::string implementation breaks tests on AArch64. [not found] <bug-64443-4@http.gcc.gnu.org/bugzilla/> 2014-12-30 17:10 ` [Bug libstdc++/64443] New std::string implementation breaks tests on AArch64 belagod at gcc dot gnu.org @ 2014-12-31 10:31 ` belagod at gcc dot gnu.org 2014-12-31 12:02 ` belagod at gcc dot gnu.org ` (3 subsequent siblings) 5 siblings, 0 replies; 6+ messages in thread From: belagod at gcc dot gnu.org @ 2014-12-31 10:31 UTC (permalink / raw) To: gcc-bugs https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64443 --- Comment #4 from Tejas Belagod <belagod at gcc dot gnu.org> --- (In reply to Andrew Pinski from comment #1) > >This commit seems to be breaking libstdc++-v3 runs on AArch64. > > Is this under Linux or with newlib? It works fine under Linux. ^ permalink raw reply [flat|nested] 6+ messages in thread
* [Bug libstdc++/64443] New std::string implementation breaks tests on AArch64. [not found] <bug-64443-4@http.gcc.gnu.org/bugzilla/> 2014-12-30 17:10 ` [Bug libstdc++/64443] New std::string implementation breaks tests on AArch64 belagod at gcc dot gnu.org 2014-12-31 10:31 ` belagod at gcc dot gnu.org @ 2014-12-31 12:02 ` belagod at gcc dot gnu.org 2015-02-09 0:06 ` [Bug libstdc++/64443] [5 Regression] " pinskia at gcc dot gnu.org ` (2 subsequent siblings) 5 siblings, 0 replies; 6+ messages in thread From: belagod at gcc dot gnu.org @ 2014-12-31 12:02 UTC (permalink / raw) To: gcc-bugs https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64443 --- Comment #5 from Tejas Belagod <belagod at gcc dot gnu.org> --- (In reply to Tejas Belagod from comment #3) > (In reply to Andrew Pinski from comment #1) > > >This commit seems to be breaking libstdc++-v3 runs on AArch64. > > > > Is this under Linux or with newlib? > > newlib. When run on a fast-model(simulator) they fail by raising an > exception. I'll post more info on the kind of exception rasied when I've > investigated a bit more... It is a memory fault. Looks like an invalid memory read. So, similar to PR64368, I guess. ^ permalink raw reply [flat|nested] 6+ messages in thread
* [Bug libstdc++/64443] [5 Regression] New std::string implementation breaks tests on AArch64. [not found] <bug-64443-4@http.gcc.gnu.org/bugzilla/> ` (2 preceding siblings ...) 2014-12-31 12:02 ` belagod at gcc dot gnu.org @ 2015-02-09 0:06 ` pinskia at gcc dot gnu.org 2015-02-09 2:31 ` redi at gcc dot gnu.org 2015-02-12 13:55 ` belagod at gcc dot gnu.org 5 siblings, 0 replies; 6+ messages in thread From: pinskia at gcc dot gnu.org @ 2015-02-09 0:06 UTC (permalink / raw) To: gcc-bugs https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64443 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Target Milestone|--- |5.0 Summary|[5.0 Regression] New |[5 Regression] New |std::string implementation |std::string implementation |breaks tests on AArch64. |breaks tests on AArch64. ^ permalink raw reply [flat|nested] 6+ messages in thread
* [Bug libstdc++/64443] [5 Regression] New std::string implementation breaks tests on AArch64. [not found] <bug-64443-4@http.gcc.gnu.org/bugzilla/> ` (3 preceding siblings ...) 2015-02-09 0:06 ` [Bug libstdc++/64443] [5 Regression] " pinskia at gcc dot gnu.org @ 2015-02-09 2:31 ` redi at gcc dot gnu.org 2015-02-12 13:55 ` belagod at gcc dot gnu.org 5 siblings, 0 replies; 6+ messages in thread From: redi at gcc dot gnu.org @ 2015-02-09 2:31 UTC (permalink / raw) To: gcc-bugs https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64443 --- Comment #6 from Jonathan Wakely <redi at gcc dot gnu.org> --- Are these still failing? ^ permalink raw reply [flat|nested] 6+ messages in thread
* [Bug libstdc++/64443] [5 Regression] New std::string implementation breaks tests on AArch64. [not found] <bug-64443-4@http.gcc.gnu.org/bugzilla/> ` (4 preceding siblings ...) 2015-02-09 2:31 ` redi at gcc dot gnu.org @ 2015-02-12 13:55 ` belagod at gcc dot gnu.org 5 siblings, 0 replies; 6+ messages in thread From: belagod at gcc dot gnu.org @ 2015-02-12 13:55 UTC (permalink / raw) To: gcc-bugs https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64443 Tejas Belagod <belagod at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #7 from Tejas Belagod <belagod at gcc dot gnu.org> --- Looks like all these have been fixed. Thanks! ^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2015-02-12 13:55 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
[not found] <bug-64443-4@http.gcc.gnu.org/bugzilla/>
2014-12-30 17:10 ` [Bug libstdc++/64443] New std::string implementation breaks tests on AArch64 belagod at gcc dot gnu.org
2014-12-31 10:31 ` belagod at gcc dot gnu.org
2014-12-31 12:02 ` belagod at gcc dot gnu.org
2015-02-09 0:06 ` [Bug libstdc++/64443] [5 Regression] " pinskia at gcc dot gnu.org
2015-02-09 2:31 ` redi at gcc dot gnu.org
2015-02-12 13:55 ` belagod at gcc dot gnu.org
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).