public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pluto at agmk dot net" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug other/39979] [4.4/4.5/4.6 Regression] possible wrong code at all -0x levels. Date: Tue, 11 May 2010 22:50:00 -0000 [thread overview] Message-ID: <20100511225008.4666.qmail@sourceware.org> (raw) In-Reply-To: <bug-39979-7667@http.gcc.gnu.org/bugzilla/> ------- Comment #14 from pluto at agmk dot net 2010-05-11 22:50 ------- few hours of git-bisecting and i have first bad commit: 3bfe8549d7fd3c67c90f64e76cbf60daae1e211c is the first bad commit commit 3bfe8549d7fd3c67c90f64e76cbf60daae1e211c Author: bkoz <bkoz@138bc75d-0d04-0410-961f-82ee72b054a4> Date: Tue Jan 13 01:49:30 2009 +0000 2009-01-12 Benjamin Kosnik <bkoz@redhat.com> PR libstdc++/38384 * crossconfig.m4 (hpux): Update for 10.20, 11, 11.20. * configure: Regenerate. 2009-01-12 Benjamin Kosnik <bkoz@redhat.com> * crossconfig.m4 (linux): Add GCC_CHECK_TLS to define _GLIBCXX_HAVE_TLS. Use GLIBCXX_CHECK_COMPILER_FEATURES to compute SECTION_FLAGS. git-svn-id: svn+ssh://gcc.gnu.org/svn/gcc/trunk@143322 138bc75d-0d04-0410-961f-82ee72b054a4 this change in some way breaks static version of STLport-5.2.1 used in my app. i'll check parts of this commit... -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39979
next prev parent reply other threads:[~2010-05-11 22:50 UTC|newest] Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top 2009-04-30 17:45 [Bug other/39979] New: possible wrong code at -O0 pluto at agmk dot net 2009-11-12 10:39 ` [Bug other/39979] " pluto at agmk dot net 2010-04-17 13:59 ` [Bug other/39979] possible wrong code at all -0x levels pluto at agmk dot net 2010-04-18 13:34 ` pluto at agmk dot net 2010-04-18 13:44 ` pluto at agmk dot net 2010-04-18 18:30 ` rguenth at gcc dot gnu dot org 2010-04-18 19:01 ` pluto at agmk dot net 2010-04-18 19:04 ` pluto at agmk dot net 2010-04-18 20:28 ` pluto at agmk dot net 2010-04-18 20:32 ` rguenth at gcc dot gnu dot org 2010-04-18 20:33 ` rguenth at gcc dot gnu dot org 2010-04-19 10:09 ` [Bug other/39979] [4.4/4.5/4.6 Regression] " rguenth at gcc dot gnu dot org 2010-04-19 11:44 ` pluto at agmk dot net 2010-04-19 11:45 ` pluto at agmk dot net 2010-04-20 12:21 ` pluto at agmk dot net 2010-04-30 8:57 ` jakub at gcc dot gnu dot org 2010-05-11 22:50 ` pluto at agmk dot net [this message] 2010-05-12 13:57 ` pluto at agmk dot net 2010-05-12 20:27 ` pluto at agmk dot net 2010-05-12 20:55 ` [Bug other/39979] [4.4/4.5/4.6 Regression] libsupc++(eh_globals.cc)/stlport TLS incompatibility pinskia at gcc dot gnu dot org 2010-05-13 9:14 ` pluto at agmk dot net 2010-05-13 10:25 ` redi at gcc dot gnu dot org 2010-05-13 10:46 ` pluto at agmk dot net 2010-05-13 11:29 ` redi at gcc dot gnu dot org
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20100511225008.4666.qmail@sourceware.org \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
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).