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/14235] [3.4/3.5 Regression] ICE in verify_local_live_at start (flow.c:546)
Date: Mon, 01 Mar 2004 07:53:00 -0000 [thread overview]
Message-ID: <20040301075344.25521.qmail@sources.redhat.com> (raw)
In-Reply-To: <20040221043216.14235.senor_fjord@yahoo.com>
------- Additional Comments From ebotcazou at gcc dot gnu dot org 2004-03-01 07:53 -------
> | I'll not use the same wording the next time I lower a priority. But,
> | frankly, when you see
> |
> | long long a;
> |
> | scanf("%d",a);
> |
> | if (!a) {
> |
> | you sometimes can't help doing so.
>
> Not if you tried initialization to see whether that it where it comes
> from. It is fair to assume that GCC developers (including the bug
> masters!) know GCC is a labyrinth; keeping lecturing people on that
> does not help either.
Sorry, but I fail to see what you mean in the first sentence (not because of the
typo). As for the second sentence, well, maybe; but keeping overreacting does
not help either :-)
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14235
next prev parent reply other threads:[~2004-03-01 7:53 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-21 4:32 [Bug c/14235] New: ICE in verify_local_live_at start (flow.c:546) on 2004-02-18 snapshot senor_fjord at yahoo dot com
2004-02-21 4:37 ` [Bug c/14235] " senor_fjord at yahoo dot com
2004-02-22 17:22 ` [Bug optimization/14235] " senor_fjord at yahoo dot com
2004-02-23 1:00 ` [Bug optimization/14235] [3.4/3.5 Regression] " pinskia at gcc dot gnu dot org
2004-02-26 17:53 ` [Bug optimization/14235] [3.4/3.5 Regression] ICE in verify_local_live_at start (flow.c:546) pinskia at gcc dot gnu dot org
2004-02-26 18:00 ` Christian Ehrhardt
2004-02-26 17:58 ` pinskia at gcc dot gnu dot org
2004-02-26 18:00 ` ehrhardt at mathematik dot uni-ulm dot de
2004-02-26 18:03 ` pinskia at gcc dot gnu dot org
2004-02-28 14:07 ` ebotcazou at gcc dot gnu dot org
2004-02-29 18:15 ` ebotcazou at gcc dot gnu dot org
2004-02-29 19:42 ` pinskia at gcc dot gnu dot org
2004-02-29 20:24 ` senor_fjord at yahoo dot com
2004-02-29 22:36 ` ebotcazou at gcc dot gnu dot org
2004-03-01 5:24 ` senor_fjord at yahoo dot com
2004-03-01 5:29 ` pinskia at gcc dot gnu dot org
2004-03-01 6:01 ` bangerth at dealii dot org
2004-03-01 6:43 ` ebotcazou at gcc dot gnu dot org
2004-03-01 7:29 ` gdr at integrable-solutions dot net
2004-03-01 7:53 ` ebotcazou at gcc dot gnu dot org [this message]
2004-03-01 8:10 ` gdr at integrable-solutions dot net
2004-03-01 8:53 ` ebotcazou at gcc dot gnu dot org
2004-03-01 12:31 ` ebotcazou at gcc dot gnu dot org
2004-03-01 15:20 ` bangerth at dealii dot org
2004-03-01 15:37 ` gdr at integrable-solutions dot net
2004-03-01 16:13 ` ebotcazou at gcc dot gnu dot org
2004-03-04 9:01 ` cvs-commit at gcc dot gnu dot org
2004-03-04 9:23 ` cvs-commit at gcc dot gnu dot org
2004-03-04 10:22 ` ebotcazou at gcc dot gnu dot org
2004-04-02 12:18 ` jakub at gcc dot gnu dot org
2004-04-13 21:04 ` cvs-commit at gcc dot gnu dot org
2004-04-29 6:30 ` 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=20040301075344.25521.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).