public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenther at suse dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/53708] [4.8 Regression] Many failures of the objc tests with -O3 -fnext-runtime and -m32
Date: Tue, 30 Oct 2012 17:11:00 -0000 [thread overview]
Message-ID: <bug-53708-4-AQsaZ8XudZ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-53708-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53708
--- Comment #10 from rguenther at suse dot de <rguenther at suse dot de> 2012-10-30 17:10:52 UTC ---
On Tue, 30 Oct 2012, bergner at gcc dot gnu.org wrote:
>
> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53708
>
> Peter Bergner <bergner at gcc dot gnu.org> changed:
>
> What |Removed |Added
> ----------------------------------------------------------------------------
> Status|RESOLVED |REOPENED
> CC| |bergner at gcc dot gnu.org
> Resolution|FIXED |
>
> --- Comment #9 from Peter Bergner <bergner at gcc dot gnu.org> 2012-10-30 15:47:57 UTC ---
> Richard, I'm seeing this same bug in GCC 4.7 on powerpc64-linux when compiling
> GLIBC. Is there a chance we can get your patch backported to 4.7? I
> bootstrapped and regtested the backport with no regressions and can confirm it
> fixes the bug I'm running into, which can be seen with the reduced test case
> from glibc:
>
> bergner@bns:~/gcc/BUGS> cat foo.i
> static void (*const init_array []) (void)
> __attribute__ ((section (".init_array"), aligned (sizeof (void *)), used))
> = { 0 };
>
> bergner@bns:~/gcc/BUGS> /home/bergner/gcc/build/gcc-fsf-4_7-base/gcc/xgcc
> -B/home/bergner/gcc/build/gcc-fsf-4_7-base/gcc -S -m64 -O3 -maltivec foo.i -o
> bad.s
>
> bergner@bns:~/gcc/BUGS> /home/bergner/gcc/build/gcc-fsf-4_7-pr53708/gcc/xgcc
> -B/home/bergner/gcc/build/gcc-fsf-4_7-pr53708/gcc -S -m64 -O3 -maltivec foo.i
> -o good.s
>
> bergner@bns:~/gcc/BUGS> diff -u bad.s good.s
> --- bad.s 2012-10-30 10:41:15.000000000 -0500
> +++ good.s 2012-10-30 10:41:23.000000000 -0500
> @@ -2,7 +2,7 @@
> .section ".toc","aw"
> .section ".text"
> .section .init_array,"a"
> - .align 4
> + .align 3
> .type init_array, @object
> .size init_array, 8
> init_array:
>
> The above is bad, because the extra alignment causes the linker to add some
> null padding to the init_array and the loader isn't expecting that and ends up
> segv'ing.
Certainly - but can you check there wasn't a followup for fallout?
ISTR something here ...
next prev parent reply other threads:[~2012-10-30 17:11 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-17 13:29 [Bug tree-optimization/53708] New: " dominiq at lps dot ens.fr
2012-06-17 14:13 ` [Bug tree-optimization/53708] " iains at gcc dot gnu.org
2012-06-18 8:52 ` [Bug middle-end/53708] " rguenth at gcc dot gnu.org
2012-06-18 10:00 ` dominiq at lps dot ens.fr
2012-06-18 12:42 ` dominiq at lps dot ens.fr
2012-06-18 20:11 ` iains at gcc dot gnu.org
2012-06-19 8:47 ` dominiq at lps dot ens.fr
2012-06-19 9:19 ` rguenth at gcc dot gnu.org
2012-06-19 9:21 ` rguenth at gcc dot gnu.org
2012-10-30 15:48 ` bergner at gcc dot gnu.org
2012-10-30 17:11 ` rguenther at suse dot de [this message]
2012-10-30 18:27 ` bergner at gcc dot gnu.org
2012-10-30 18:38 ` jakub at gcc dot gnu.org
2012-10-31 15:33 ` law at redhat dot com
2012-11-01 2:48 ` bergner at gcc dot gnu.org
2012-11-03 14:02 ` bergner at gcc dot gnu.org
2012-11-03 14:06 ` bergner 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-53708-4-AQsaZ8XudZ@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).