public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "fxcoudert at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/63890] New: [4.9/5.0 regression] Compiling trivial program with -O -p leads to misaligned stack
Date: Sat, 15 Nov 2014 15:19:00 -0000	[thread overview]
Message-ID: <bug-63890-4@http.gcc.gnu.org/bugzilla/> (raw)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63890

            Bug ID: 63890
           Summary: [4.9/5.0 regression] Compiling trivial program with -O
                    -p leads to misaligned stack
           Product: gcc
           Version: 5.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: target
          Assignee: unassigned at gcc dot gnu.org
          Reporter: fxcoudert at gcc dot gnu.org

Created attachment 33985
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=33985&action=edit
Assembler generated by trunk compiler with "-m32 -O -p"

Compile the following trivial program with trunk (rev. 217599) or the released
4.9.2 gcc leads to runtime segfault, on x86_64-apple-darwin14:

$ cat a.c
int main (void) { __builtin_exit (0); }
$ ./bin/gcc -m32 -O -p a.c && ./a.out
zsh: segmentation fault  ./a.out

This shows up as a failure of gcc.dg/20021014-1.c in the testsuite results
(https://gcc.gnu.org/ml/gcc-testresults/2014-11/msg01533.html).

Removing -p, or -O, or compiling for 64-bit doesn't trigger the bug. The
backtrace is:

  * frame #0: 0x9036f440 libdyld.dylib`misaligned_stack_error_
    frame #1: 0x00001f75 a.out`main + 17
    frame #2: 0x903716d9 libdyld.dylib`start + 1

Comparing the generated assembly by the trunk compiler (bad-trunk.s) with that
generated by the 4.8.3 compiler (ok-48.s) shows the difference is simple:

--- ok-48.s    2014-11-15 16:17:55.000000000 +0100
+++ bad-trunk.s    2014-11-15 16:17:44.000000000 +0100
@@ -1,4 +1,4 @@
-    .text
+    .section __TEXT,__text_startup,regular,pure_instructions
     .globl _main
 _main:
 LFB0:
@@ -7,12 +7,12 @@ LCFI0:
     movl    %esp, %ebp
 LCFI1:
     pushl    %ebx
-    subl    $20, %esp
+    subl    $16, %esp
 LCFI2:
     call    ___x86.get_pc_thunk.bx
 L1$pb:
     call mcount
-    movl    $0, (%esp)
+    pushl    $0
     call    _exit
 LFE0:
     .section __TEXT,__textcoal_nt,coalesced,pure_instructions


             reply	other threads:[~2014-11-15 15:19 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-15 15:19 fxcoudert at gcc dot gnu.org [this message]
2014-11-15 15:20 ` [Bug target/63890] " fxcoudert at gcc dot gnu.org
2014-11-15 15:45 ` fxcoudert at gcc dot gnu.org
2014-11-15 16:01 ` iains at gcc dot gnu.org
2014-11-15 16:24 ` dominiq at lps dot ens.fr
2014-11-15 16:42 ` dominiq at lps dot ens.fr
2014-11-15 16:46 ` iains at gcc dot gnu.org
2014-11-15 18:11 ` iains at gcc dot gnu.org
2014-11-17  9:32 ` rguenth at gcc dot gnu.org
2014-11-24 16:58 ` rguenth at gcc dot gnu.org
2015-02-24 22:41 ` [Bug target/63890] [4.9/5 " mrs at gcc dot gnu.org
2015-02-25  2:16 ` mrs at gcc dot gnu.org
2015-02-25  4:24 ` mrs at gcc dot gnu.org
2015-02-25  6:46 ` hubicka at ucw dot cz
     [not found] ` <bug-63890-4-n8faGCUNTz@http.gcc.gnu.org/bugzilla/>
2015-02-27  8:29   ` Jan Hubicka
2015-02-27  8:38 ` hubicka at ucw dot cz
2015-03-01 20:42 ` howarth at bromo dot med.uc.edu
2015-03-01 22:02 ` hubicka at gcc dot gnu.org
2015-03-01 23:19 ` mrs at gcc dot gnu.org
2015-03-01 23:26 ` hubicka at ucw dot cz
2015-03-01 23:49 ` mrs at gcc dot gnu.org
2015-03-02  0:29 ` hubicka at ucw dot cz
2015-03-30 13:17 ` iains at gcc dot gnu.org
2015-04-02  9:15 ` dominiq at lps dot ens.fr
2015-06-26 20:07 ` [Bug target/63890] [4.9/5/6 " jakub at gcc dot gnu.org
2015-06-26 20:36 ` jakub 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-63890-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).