public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/61904] Incorrect stack red-zoning on x86-64 code generation
Date: Fri, 25 Jul 2014 09:27:00 -0000	[thread overview]
Message-ID: <bug-61904-4-EluObnFIRM@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-61904-4@http.gcc.gnu.org/bugzilla/>

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

Richard Biener <rguenth at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|WAITING                     |UNCONFIRMED
     Ever confirmed|1                           |0

--- Comment #5 from Richard Biener <rguenth at gcc dot gnu.org> ---
With both the FSF 4.9.0 and 4.9.1 releases and

gcc -S t.i -mno-80387 -mno-fp-ret-in-387 -mpreferred-stack-boundary=3
-mtune=generic -mno-red-zone -mcmodel=kernel -maccumulate-outgoing-args
-mno-sse -mno-mmx -mno-sse2 -mno-3dnow -mno-avx -march=x86-64 -g -Os
-fno-strict-aliasing -fno-common -fno-asynchronous-unwind-tables
-fno-omit-frame-pointer

(too many options only to guess from the .s file - can you please specify
explicitely passed options?)


load_balance:
.LFB2409:
        .loc 2 6487 0
.LVL1260:
        pushq   %rbp
.LCFI442:
        movq    %rsp, %rbp
.LCFI443:
        pushq   %r15
        pushq   %r14
        pushq   %r13
        pushq   %r12
.LCFI444:
        movq    %rdx, %r12
        pushq   %rbx
.LBB2812:
        .loc 2 6493 0
        movq    $load_balance_mask, -376(%rbp)
.LBE2812:
        .loc 2 6487 0
        subq    $416, %rsp
.LCFI445:
        .loc 2 6489 0
        movq    (%rdx), %rax
        .loc 2 6487 0
        movl    %edi, -392(%rbp)
        movl    %ecx, -388(%rbp)
        movq    %r8, -456(%rbp)
        .loc 2 6489 0
        movq    %rax, -424(%rbp)
.LVL1261:
.LBB2813:
        .loc 2 6493 0
        movq    -376(%rbp), %rax
.LVL1262:
#APP
# 6493 "kernel/sched/fair.c" 1
        add %gs:this_cpu_off, %rax
# 0 "" 2
#NO_APP


which I guess is equally bad (even if not matching the output from Michel).
It seems to be triggered by -g or -fvar-tracking and is fixed on the 4.9
branch - so it might be a duplicate of PR61801.


  parent reply	other threads:[~2014-07-25  9:27 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-25  8:09 [Bug c/61904] New: " torvalds@linux-foundation.org
2014-07-25  8:11 ` [Bug c/61904] " torvalds@linux-foundation.org
2014-07-25  8:17 ` [Bug target/61904] " trippels at gcc dot gnu.org
2014-07-25  8:18 ` torvalds@linux-foundation.org
2014-07-25  8:24 ` torvalds@linux-foundation.org
2014-07-25  9:27 ` rguenth at gcc dot gnu.org [this message]
2014-07-25  9:33 ` rguenth at gcc dot gnu.org
2014-07-25 18:12 ` torvalds@linux-foundation.org
2014-07-25 18:19 ` torvalds@linux-foundation.org
2014-07-25 18:42 ` pinskia at gcc dot gnu.org
2014-07-25 19:01 ` torvalds@linux-foundation.org
2014-07-26 10:02 ` trippels 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-61904-4-EluObnFIRM@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).