public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rth at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/13245] [3.3/3.4/3.5 Regression] SIGBUS (alignment) on ia-32 if alignment trapping is enabled
Date: Fri, 30 Jan 2004 09:52:00 -0000 [thread overview]
Message-ID: <20040130095214.7107.qmail@sources.redhat.com> (raw)
In-Reply-To: <20031130202210.13245.gcc-bug@vogtner.de>
------- Additional Comments From rth at gcc dot gnu dot org 2004-01-30 09:52 -------
Not a regression, nor a bug. -maligned-double does *not* affect
parameter lists.
The call to operator<< has two arguments, the first is a 4 byte pointer,
and the second is a double. The double will *always* be at sp+4, which
will always be misaligned if we're trying to keep the regular stack frame
aligned.
If gcc 2.95 passed this test, it's only because it moved the 3.0 to the
stack with integer move instructions. Change the test to use the result
of real floating-point arithmetic and it will fail too.
--
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |INVALID
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=13245
next prev parent reply other threads:[~2004-01-30 9:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-30 20:22 [Bug c++/13245] New: " gcc-bug at vogtner dot de
2003-11-30 20:23 ` [Bug c++/13245] " gcc-bug at vogtner dot de
2003-11-30 20:23 ` gcc-bug at vogtner dot de
2003-11-30 20:29 ` pinskia at gcc dot gnu dot org
2003-11-30 20:48 ` gcc-bug at vogtner dot de
2004-01-30 4:26 ` pinskia at gcc dot gnu dot org
2004-01-30 4:29 ` [Bug c++/13245] [3.3/3.4/3.5 Regression] " pinskia at gcc dot gnu dot org
2004-01-30 9:52 ` rth at gcc dot gnu dot org [this message]
2004-01-30 16:24 ` gcc-bug at vogtner dot de
2004-01-31 0:20 ` rth at gcc dot gnu dot 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=20040130095214.7107.qmail@sources.redhat.com \
--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).