public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "echristo at redhat dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/16266] [4.0 regression] gcc.dg/c99-intconst-1.c compilation is very slow
Date: Thu, 07 Oct 2004 06:48:00 -0000 [thread overview]
Message-ID: <20041007064840.23822.qmail@sourceware.org> (raw)
In-Reply-To: <20040629130803.16266.amylaar@gcc.gnu.org>
------- Additional Comments From echristo at redhat dot com 2004-10-07 06:48 -------
Subject: Re: [4.0 regression]
gcc.dg/c99-intconst-1.c compilation is very slow
On Thu, 2004-10-07 at 00:44, Joern Rennecke wrote:
> >
> >
> > ------- Additional Comments From giovannibajo at libero dot it 2004-10-06 23:19 -------
> > I cannot reproduce this on mainline 20040923 on x86-linux with a disable
> > checking compiler. So either:
> >
> > - the bug is already fixed
> > - the bug only appears crossing to sh-elf
> > - the bug does not exist with disable-checking so we do not care
> > (should we?)
> >
> > Joern, can you please check which of the three above applies?
>
> That is had to check at the moment:
>
> ../../srcw/gcc/config/sh/sh.c:9416: `DW_CC_renesas_sh' undeclared (first use in this function)
> ../../srcw/gcc/config/sh/sh.c:9416: (Each undeclared identifier is reported only once
> ../../srcw/gcc/config/sh/sh.c:9416: for each function it appears in.)
> make[1]: *** [sh.o] Error 1
> make[1]: Leaving directory `/swbuild/nightly/2004-10-07/sh-elf/gcc'
> make: *** [all-gcc] Error 2
Fixed thusly. Sorry about that.
2004-10-06 Eric Christopher <echristo@redhat.com>
* config/sh/sh.c (sh_dwarf_calling_convention): Fix renesas dwarf
attribute.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=16266
next prev parent reply other threads:[~2004-10-07 6:48 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-29 14:08 [Bug regression/16266] New: 3.5 regression: " amylaar at gcc dot gnu dot org
2004-06-29 14:34 ` [Bug regression/16266] [3.5 regression] " pinskia at gcc dot gnu dot org
2004-06-29 14:39 ` reichelt at gcc dot gnu dot org
2004-06-29 16:06 ` joern dot rennecke at superh dot com
2004-06-29 17:05 ` joern dot rennecke at superh dot com
2004-08-15 3:30 ` [Bug middle-end/16266] " pinskia at gcc dot gnu dot org
2004-10-06 23:19 ` [Bug middle-end/16266] [4.0 " giovannibajo at libero dot it
2004-10-07 6:44 ` amylaar at spamcop dot net
2004-10-07 6:48 ` echristo at redhat dot com [this message]
2004-10-08 9:17 ` amylaar at spamcop dot net
2004-10-08 11:57 ` pinskia at gcc dot gnu dot org
2004-10-08 23:11 ` joern dot rennecke at superh-support dot com
2004-10-08 23:32 ` Diego Novillo
2004-10-08 23:32 ` dnovillo at redhat dot com
2004-10-09 1:58 ` amylaar at spamcop dot net
2004-10-09 2:01 ` pinskia at gcc dot gnu dot org
2004-10-09 2:51 ` pinskia at gcc dot gnu dot org
2004-10-09 3:32 ` pinskia at gcc dot gnu dot org
2004-10-09 3:43 ` pinskia at gcc dot gnu dot org
2004-10-09 4:27 ` pinskia at gcc dot gnu dot org
2004-10-09 4:48 ` pinskia at gcc dot gnu dot org
2004-10-09 5:04 ` pinskia at gcc dot gnu dot org
2004-10-11 18:32 ` pinskia at gcc dot gnu dot org
2004-10-11 18:32 ` cvs-commit at gcc dot gnu dot org
2004-11-17 18:02 ` fjahanian at apple dot com
2004-11-17 18:14 ` pinskia at gcc dot gnu dot org
2004-11-17 18:17 ` pinskia 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=20041007064840.23822.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).