public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dominiq at lps dot ens dot fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/34621] [4.3 Regression] gcc.c-torture/execute/va-arg-25.c:32: internal compiler error: in expand_call, at calls.c:2785
Date: Wed, 13 Feb 2008 16:08:00 -0000	[thread overview]
Message-ID: <20080213160747.29865.qmail@sourceware.org> (raw)
In-Reply-To: <bug-34621-12313@http.gcc.gnu.org/bugzilla/>



------- Comment #19 from dominiq at lps dot ens dot fr  2008-02-13 16:07 -------
I am quite confused by the following:

>> STACK_BOUNDARY to 128,
>> while linux to 4.
>>
...
> If you do not align the stack at a 128-bit boundary, your program will  
> crash.  The hardware that it is related to is SSE2.

In which unit is expressed STACK_BOUNDARY? If linux set it to 4, is it correct
to understand that it is bytes and not bits (4 bits would not make any sense)?
Now, if Darwin requires 128 bits, should not the value be 16?


-- 


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


  parent reply	other threads:[~2008-02-13 16:08 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-30 11:25 [Bug c/34621] New: " dominiq at lps dot ens dot fr
2008-01-13 15:27 ` [Bug c/34621] " rguenth at gcc dot gnu dot org
2008-01-13 17:41 ` dominiq at lps dot ens dot fr
2008-01-13 17:50 ` rguenth at gcc dot gnu dot org
2008-01-20  4:58 ` [Bug middle-end/34621] " pinskia at gcc dot gnu dot org
2008-01-21 15:31 ` jakub at gcc dot gnu dot org
2008-01-21 15:37 ` jakub at gcc dot gnu dot org
2008-01-21 15:52 ` jakub at gcc dot gnu dot org
2008-01-21 16:43 ` jsm28 at gcc dot gnu dot org
2008-01-21 17:11 ` geoffk at gcc dot gnu dot org
2008-01-21 18:15 ` pinskia at gcc dot gnu dot org
2008-01-21 21:01 ` jakub at gcc dot gnu dot org
2008-02-12 15:12 ` ubizjak at gmail dot com
2008-02-12 15:46 ` hjl dot tools at gmail dot com
2008-02-12 18:46 ` ubizjak at gmail dot com
2008-02-12 18:53 ` hjl dot tools at gmail dot com
2008-02-12 22:44 ` geoffk at geoffk dot org
2008-02-12 23:46 ` hjl dot tools at gmail dot com
2008-02-13  5:55 ` geoffk at geoffk dot org
2008-02-13  6:42 ` hjl dot tools at gmail dot com
2008-02-13  7:51 ` geoffk at geoffk dot org
2008-02-13 15:40 ` hjl dot tools at gmail dot com
2008-02-13 16:08 ` dominiq at lps dot ens dot fr [this message]
2008-02-13 16:19 ` ubizjak at gmail dot com
2008-02-13 16:41 ` dominiq at lps dot ens dot fr
2008-02-13 17:04 ` ubizjak at gmail dot com
2008-02-13 17:19 ` pinskia at gcc dot gnu dot org
2008-02-13 18:12 ` ubizjak at gmail dot com
2008-02-13 23:42 ` dominiq at lps dot ens dot fr
2008-02-14  6:46 ` ubizjak at gmail dot com
2008-02-14  8:13 ` jpr at csc dot fi
2008-02-14  9:46 ` dominiq at lps dot ens dot fr
2008-02-14  9:58 ` ubizjak at gmail dot com
2008-02-14 10:09 ` dominiq at lps dot ens dot fr
2008-02-14 12:49 ` ubizjak at gmail dot com
2008-02-14 17:09 ` ubizjak at gmail dot com
2008-02-14 19:37 ` dominiq at lps dot ens dot fr
2008-02-15  7:22 ` dominiq at lps dot ens dot fr
2008-02-15  8:02 ` ubizjak at gmail dot com
2008-02-15  9:57 ` uros at gcc dot gnu dot org
2008-02-15 10:02 ` ubizjak at gmail dot com

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=20080213160747.29865.qmail@sourceware.org \
    --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).