public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ebotcazou at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug optimization/13424] [3.4/3.5 Regression] gcc.dg/20031202-1.c is miscompiled
Date: Wed, 17 Mar 2004 10:13:00 -0000 [thread overview]
Message-ID: <20040317101318.6729.qmail@sources.redhat.com> (raw)
In-Reply-To: <20031218033126.13424.danglin@gcc.gnu.org>
------- Additional Comments From ebotcazou at gcc dot gnu dot org 2004-03-17 10:13 -------
Yes, actually it makes it fail everywhere!
The problem is that the C front-end is relying on the clearing optimization to
implement the semantics mandated by C99 $6.7.8 [19].
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=13424
next prev parent reply other threads:[~2004-03-17 10:13 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-18 5:22 [Bug pending/13424] New: 20031202-1.c is miscompiled on all PA ports danglin at gcc dot gnu dot org
2003-12-18 5:25 ` [Bug optimization/13424] [3.4 Regression] " pinskia at gcc dot gnu dot org
2003-12-18 16:39 ` [Bug optimization/13424] [3.4 Regression] gcc.dg/20031202-1.c is miscompiled ebotcazou at gcc dot gnu dot org
2003-12-18 19:41 ` dave at hiauly1 dot hia dot nrc dot ca
2003-12-18 20:12 ` ebotcazou at gcc dot gnu dot org
2004-01-10 7:01 ` pinskia at gcc dot gnu dot org
2004-01-10 7:14 ` pinskia at gcc dot gnu dot org
2004-01-10 20:56 ` dave at hiauly1 dot hia dot nrc dot ca
2004-01-10 21:00 ` dave at hiauly1 dot hia dot nrc dot ca
2004-01-10 21:43 ` ebotcazou at gcc dot gnu dot org
2004-01-13 11:40 ` ebotcazou at gcc dot gnu dot org
2004-01-13 11:46 ` ebotcazou at gcc dot gnu dot org
2004-01-25 17:00 ` [Bug optimization/13424] [3.4/3.5 " schwab at suse dot de
2004-01-29 8:06 ` cvs-commit at gcc dot gnu dot org
2004-02-07 9:55 ` ebotcazou at gcc dot gnu dot org
2004-02-10 18:08 ` [Bug optimization/13424] [3.4 " cvs-commit at gcc dot gnu dot org
2004-02-10 20:34 ` pinskia at gcc dot gnu dot org
2004-02-21 23:34 ` danglin at gcc dot gnu dot org
2004-02-23 8:53 ` ebotcazou at gcc dot gnu dot org
2004-02-23 8:53 ` ebotcazou at gcc dot gnu dot org
2004-02-28 11:26 ` cvs-commit at gcc dot gnu dot org
2004-03-02 23:43 ` [Bug optimization/13424] [3.4/3.5 " rth at gcc dot gnu dot org
2004-03-03 0:58 ` dave at hiauly1 dot hia dot nrc dot ca
2004-03-16 21:18 ` ebotcazou at gcc dot gnu dot org
2004-03-16 21:23 ` ebotcazou at gcc dot gnu dot org
2004-03-17 3:21 ` dave at hiauly1 dot hia dot nrc dot ca
2004-03-17 10:13 ` ebotcazou at gcc dot gnu dot org [this message]
2004-03-17 17:57 ` ebotcazou at gcc dot gnu dot org
2004-03-18 2:13 ` dave at hiauly1 dot hia dot nrc dot ca
2004-03-27 16:10 ` cvs-commit at gcc dot gnu dot org
2004-04-02 23:06 ` cvs-commit at gcc dot gnu dot org
2004-04-05 7:46 ` steven at gcc dot gnu dot org
2004-04-05 15:35 ` jakub at gcc dot gnu dot org
2004-04-05 16:24 ` dave at hiauly1 dot hia dot nrc dot ca
2004-04-05 16:41 ` cvs-commit at gcc dot gnu dot org
2004-04-05 17:58 ` ebotcazou at gcc dot gnu dot org
2004-04-06 8:52 ` mark at codesourcery dot com
2004-04-06 9:04 ` cvs-commit at gcc dot gnu dot org
2004-04-06 16:05 ` danglin at gcc dot gnu dot org
2004-04-06 16:16 ` bangerth at dealii dot org
2004-04-06 16:20 ` dave at hiauly1 dot hia dot nrc dot ca
2004-04-06 17:53 ` bangerth at dealii dot org
2004-04-06 18:08 ` dave at hiauly1 dot hia dot nrc dot ca
2004-04-06 20:44 ` bangerth at dealii dot org
2004-04-13 20:42 ` cvs-commit 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=20040317101318.6729.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).