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 debug/13367] [3.4 Regression] gcc gets an internal error when building gcc-3.4 with an installed gcc 3.4 Date: Wed, 10 Dec 2003 18:02:00 -0000 [thread overview] Message-ID: <20031210180210.9473.qmail@sources.redhat.com> (raw) In-Reply-To: <20031209135925.13367.stevenyi@163.com> ------- Additional Comments From pinskia at gcc dot gnu dot org 2003-12-10 18:02 ------- The reason why my build was able to complete and yours was not was because your 'CFLAGS=- Dinline=inline __attribute__((always_inline))"'. -- What |Removed |Added ---------------------------------------------------------------------------- Severity|normal |critical Status|WAITING |NEW Ever Confirmed| |1 Keywords| |build Last reconfirmed|0000-00-00 00:00:00 |2003-12-10 18:02:10 date| | Summary|gcc gets an internal error |[3.4 Regression] gcc gets an |when building gcc-3.4 with |internal error when building |an installed gcc 3.4 |gcc-3.4 with an installed | |gcc 3.4 Target Milestone|--- |3.4 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=13367
next prev parent reply other threads:[~2003-12-10 18:02 UTC|newest] Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-12-09 13:59 [Bug c/13367] New: " stevenyi at 163 dot com 2003-12-09 14:22 ` [Bug c/13367] " schwab at suse dot de 2003-12-09 16:01 ` [Bug debug/13367] " pinskia at gcc dot gnu dot org 2003-12-10 4:52 ` stevenyi at 163 dot com 2003-12-10 5:36 ` dhazeghi at yahoo dot com 2003-12-10 5:51 ` pinskia at gcc dot gnu dot org 2003-12-10 6:44 ` stevenyi at 163 dot com 2003-12-10 7:17 ` stevenyi at 163 dot com 2003-12-10 9:35 ` stevenyi at 163 dot com 2003-12-10 15:45 ` pinskia at gcc dot gnu dot org 2003-12-10 16:48 ` stevenyi at 163 dot com 2003-12-10 16:50 ` pinskia at gcc dot gnu dot org 2003-12-10 17:52 ` dhazeghi at yahoo dot com 2003-12-10 18:02 ` pinskia at gcc dot gnu dot org [this message] 2003-12-10 23:08 ` [Bug debug/13367] [3.4 Regression] " dhazeghi at yahoo dot com 2003-12-10 23:49 ` dhazeghi at yahoo dot com 2003-12-11 0:01 ` pinskia at gcc dot gnu dot org 2003-12-19 1:19 ` pinskia at gcc dot gnu dot org 2003-12-19 3:12 ` stevenyi at 163 dot com 2003-12-19 3:33 ` pinskia at gcc dot gnu dot org 2003-12-19 4:16 ` stevenyi at 163 dot com 2003-12-19 4:20 ` pinskia at gcc dot gnu dot org 2003-12-29 17:41 ` pinskia at gcc dot gnu dot org 2004-01-01 13:59 ` cvs-commit at gcc dot gnu dot org 2004-01-01 15:38 ` pinskia at gcc dot gnu dot org 2004-01-27 13:15 ` 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=20031210180210.9473.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: linkBe 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).