public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ebotcazou at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/50237] New: [4.7 regression] comparison failure caused by HAVE_INITFINI_ARRAY check
Date: Tue, 30 Aug 2011 13:26:00 -0000	[thread overview]
Message-ID: <bug-50237-4@http.gcc.gnu.org/bugzilla/> (raw)

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50237

             Bug #: 50237
           Summary: [4.7 regression] comparison failure caused by
                    HAVE_INITFINI_ARRAY check
    Classification: Unclassified
           Product: gcc
           Version: 4.7.0
            Status: UNCONFIRMED
          Severity: blocker
          Priority: P3
         Component: bootstrap
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: ebotcazou@gcc.gnu.org
              Host: x86_64-suse-linux
            Target: x86_64-suse-linux
             Build: x86_64-suse-linux


I have had a bootstrap comparison failure for days on x86-64/Linux:

libcpp/lex.o differs

It turns out that stage3 has

  6 .init_array   00000008  0000000000000000  0000000000000000  00003d20  2**3
                  CONTENTS, ALLOC, LOAD, RELOC, DATA

but stage2 has

  6 .ctors        00000008  0000000000000000  0000000000000000  00003d20  2**3
                  CONTENTS, ALLOC, LOAD, RELOC, DATA

That isn't surprising because HAVE_INITFINI_ARRAY isn't uniform:

eric@hermes:~/build/gcc/native> grep HAVE_INITFINI_ARRAY stage1-gcc/auto-host.h 
/* #undef HAVE_INITFINI_ARRAY */
eric@hermes:~/build/gcc/native> grep HAVE_INITFINI_ARRAY prev-gcc/auto-host.h
#define HAVE_INITFINI_ARRAY 1

i.e. despite http://gcc.gnu.org/ml/gcc-patches/2011-06/msg00659.html the check
is still applied to the host compiler, not to the target.  The base compiler is
the system compiler on OpenSuSE 11.0 and the check doesn't pass for it:

eric@hermes:~/build/gcc/native> gcc -o t t.c
eric@hermes:~/build/gcc/native> ./t
Aborted

The compiler is configured with

eric@hermes:~/build/gcc/native> gcc/xgcc -v
Using built-in specs.
COLLECT_GCC=gcc/xgcc
Target: x86_64-suse-linux
Configured with: /home/eric/svn/gcc/configure x86_64-suse-linux
--prefix=/home/eric/install/gcc
--with-as=/home/eric/build/binutils/native/gas/as-new
--with-ld=/home/eric/build/binutils/native/ld/ld-new
--enable-languages=c,c++,objc,obj-c++,java,fortran,ada
--enable-checking=yes,rtl --enable-__cxa_atexit --disable-nls
--disable-libmudflap
Thread model: posix
gcc version 4.7.0 20110830 (experimental) [trunk revision 178287] (GCC)


A workaround would be to get rid of the __attribute__((constructor)) in lex.c
but someone should sit down and write a correct HAVE_INITFINI_ARRAY check.


             reply	other threads:[~2011-08-30 13:20 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-30 13:26 ebotcazou at gcc dot gnu.org [this message]
2011-08-30 13:41 ` [Bug bootstrap/50237] " rguenth at gcc dot gnu.org
2011-08-30 13:50 ` rguenth at gcc dot gnu.org
2011-08-30 13:51 ` hjl.tools at gmail dot com
2011-08-30 13:58 ` ebotcazou at gcc dot gnu.org
2011-08-30 14:07 ` hjl.tools at gmail dot com
2011-08-30 14:23 ` rguenth at gcc dot gnu.org
2011-08-30 14:34 ` hjl.tools at gmail dot com
2011-08-30 15:30 ` ebotcazou at gcc dot gnu.org
2011-08-30 15:57 ` joseph at codesourcery dot com
2011-08-30 16:30 ` hjl.tools at gmail dot com
2011-08-30 16:36 ` hjl.tools at gmail dot com
2011-08-30 16:57 ` joseph at codesourcery dot com
2011-08-31  7:04 ` hjl.tools at gmail dot com
2011-08-31 15:46 ` joseph at codesourcery dot com
2011-08-31 15:47 ` hjl.tools at gmail dot com
2011-08-31 16:20 ` joseph at codesourcery dot com
2011-09-02 18:10 ` hjl.tools at gmail dot com
2011-09-03  9:32 ` [Bug bootstrap/50237] [4.7 regression] bootstrap comparison failure for libcpp/lex.o ebotcazou at gcc dot gnu.org
2011-09-03 17:17 ` hjl.tools at gmail dot com
2011-09-10 15:03 ` hjl.tools at gmail dot com
2011-10-04 13:57 ` ro at gcc dot gnu.org
2011-11-22 17:59 ` ro at CeBiTec dot Uni-Bielefeld.DE
2011-11-22 18:03 ` hjl.tools at gmail dot com
2011-11-22 18:21 ` ro at CeBiTec dot Uni-Bielefeld.DE
2011-11-22 18:35 ` hjl.tools at gmail dot com
2011-11-23 16:30 ` ro at CeBiTec dot Uni-Bielefeld.DE
2011-11-23 16:52 ` hjl.tools at gmail dot com
2011-11-23 17:17 ` ro at CeBiTec dot Uni-Bielefeld.DE
2011-11-23 17:20 ` hjl.tools at gmail dot com
2011-11-24 18:07 ` ro at CeBiTec dot Uni-Bielefeld.DE
2011-11-28 15:20 ` jakub at gcc dot gnu.org
2011-11-28 16:03 ` ro at CeBiTec dot Uni-Bielefeld.DE
2011-12-01 20:26 ` ebotcazou at gcc dot gnu.org
2011-12-07 22:06 ` jakub at gcc dot gnu.org
2012-01-09  0:54 ` pinskia at gcc dot gnu.org
2012-01-09 14:31 ` rguenth at gcc dot gnu.org
2012-01-17 16:06 ` jakub at gcc dot gnu.org
2012-01-19 10:49 ` jakub at gcc dot gnu.org
2012-01-19 10:55 ` jakub at gcc dot gnu.org
2012-01-19 16:26 ` ro at CeBiTec dot Uni-Bielefeld.DE
2012-01-19 16:32 ` jakub at gcc dot gnu.org
2012-01-19 16:41 ` ro at CeBiTec dot Uni-Bielefeld.DE
2012-01-19 16:51 ` jakub at gcc dot gnu.org
2012-01-19 16:54 ` ro at CeBiTec dot Uni-Bielefeld.DE
2012-01-20  0:25 ` pinskia at gcc dot gnu.org
2012-02-22 22:10 ` jingyu at gcc dot gnu.org
2012-02-22 22:31 ` jingyu at gcc dot gnu.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=bug-50237-4@http.gcc.gnu.org/bugzilla/ \
    --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: link
Be 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).