public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "dje at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug bootstrap/53300] [4.8 Regression] AIX bootstrap related to varpool patch Date: Fri, 11 May 2012 15:46:00 -0000 [thread overview] Message-ID: <bug-53300-4-vrDMo93jw8@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-53300-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53300 --- Comment #16 from David Edelsohn <dje at gcc dot gnu.org> 2012-05-11 15:11:59 UTC --- The mis-compiled file is libcpp/line-map.c. I have attached the pre-processed output for line-map.c on AIX. I also have attached assembly files showing the correct and incorrect output. The difference is: --- line-map.s.good 2012-05-11 11:01:33.000000000 -0400 +++ line-map.s.bad 2012-05-11 11:00:43.000000000 -0400 @@ -4536,26 +4536,6 @@ .byte 10 .byte "Macro line maps" .byte 10, 0 - .space 2 -LC..0: - .byte "LC_ENTER" - .byte 0 - .space 3 -LC..1: - .byte "LC_LEAVE" - .byte 0 - .space 3 -LC..2: - .byte "LC_RENAME" - .byte 0 - .space 2 -LC..3: - .byte "LC_RENAME_VERBATIM" - .byte 0 - .space 1 -LC..4: - .byte "LC_ENTER_MACRO" - .byte 0 .csect _linemap.rw_[RW],4 .align 2 .set LANCHOR..1,$ + 0 which corresponds to enum lc_reason { LC_ENTER = 0, LC_LEAVE, LC_RENAME, LC_RENAME_VERBATIM, LC_ENTER_MACRO };
next prev parent reply other threads:[~2012-05-11 15:12 UTC|newest] Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-05-09 19:38 [Bug bootstrap/53300] New: " dje at gcc dot gnu.org 2012-05-09 19:42 ` [Bug bootstrap/53300] " dje at gcc dot gnu.org 2012-05-10 7:33 ` [Bug bootstrap/53300] [4.8 Regression] " rguenth at gcc dot gnu.org 2012-05-10 12:17 ` ro at gcc dot gnu.org 2012-05-10 13:24 ` dje at gcc dot gnu.org 2012-05-10 17:50 ` hubicka at gcc dot gnu.org 2012-05-10 18:31 ` hubicka at gcc dot gnu.org 2012-05-10 19:47 ` dje at gcc dot gnu.org 2012-05-10 20:47 ` dje at gcc dot gnu.org 2012-05-10 20:55 ` hubicka at ucw dot cz 2012-05-10 22:43 ` ebotcazou at gcc dot gnu.org 2012-05-10 23:12 ` hubicka at ucw dot cz 2012-05-11 8:45 ` hubicka at gcc dot gnu.org 2012-05-11 10:49 ` ro at CeBiTec dot Uni-Bielefeld.DE 2012-05-11 15:11 ` dje at gcc dot gnu.org 2012-05-11 15:11 ` dje at gcc dot gnu.org 2012-05-11 15:12 ` dje at gcc dot gnu.org 2012-05-11 15:46 ` dje at gcc dot gnu.org [this message] 2012-05-11 15:49 ` dje at gcc dot gnu.org 2012-09-07 11:46 ` rguenth at gcc dot gnu.org 2012-11-15 3:18 ` pinskia at gcc dot gnu.org 2012-11-15 14:04 ` dje at gcc dot gnu.org 2013-01-15 13:55 ` rguenth at gcc dot gnu.org 2013-01-15 18:24 ` hubicka 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-53300-4-vrDMo93jw8@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: 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).