public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug regression/19813] [4.0 Regression] wrong code with -finline-limit
Date: Wed, 09 Feb 2005 08:51:00 -0000 [thread overview]
Message-ID: <20050209004806.17607.qmail@sourceware.org> (raw)
In-Reply-To: <20050207230934.19813.ctsa@u.washington.edu>
------- Additional Comments From pinskia at gcc dot gnu dot org 2005-02-09 00:48 -------
(In reply to comment #5)
> This is somewhat shorter, though maybe not much:
Does -fno-strict-aliasing make this compile and run correctly?
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19813
next prev parent reply other threads:[~2005-02-09 0:48 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-08 10:42 [Bug c++/19813] New: gcc 4.0 regression: bad code generation?? due to inlining?? ctsa at u dot washington dot edu
2005-02-08 12:00 ` [Bug c++/19813] " ctsa at u dot washington dot edu
2005-02-08 13:24 ` [Bug regression/19813] [4.0 Regression] " pinskia at gcc dot gnu dot org
2005-02-08 13:27 ` pinskia at gcc dot gnu dot org
2005-02-09 4:11 ` neroden at gcc dot gnu dot org
2005-02-09 6:42 ` bangerth at dealii dot org
2005-02-09 6:51 ` [Bug regression/19813] [4.0 Regression] wrong code with -finline-limit bangerth at dealii dot org
2005-02-09 8:51 ` pinskia at gcc dot gnu dot org [this message]
2005-02-09 9:19 ` pinskia at gcc dot gnu dot org
2005-02-15 21:09 ` jakub at gcc dot gnu dot org
2005-02-15 21:15 ` jakub at gcc dot gnu dot org
2005-02-15 21:18 ` jakub at gcc dot gnu dot org
2005-02-15 21:20 ` jakub at gcc dot gnu dot org
2005-02-15 21:46 ` [Bug c++/19813] " rth at gcc dot gnu dot org
2005-02-16 16:59 ` jakub at gcc dot gnu dot org
2005-02-18 16:16 ` cvs-commit at gcc dot gnu dot org
2005-02-18 16:27 ` jakub 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=20050209004806.17607.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).