public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Manuel Serrano <Manuel.Serrano@sophia.inria.fr>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: c/8108: Problem in the code generator for C and the linker is extremelly slow
Date: Fri, 25 Oct 2002 00:16:00 -0000 [thread overview]
Message-ID: <20021025071602.18181.qmail@sources.redhat.com> (raw)
The following reply was made to PR c/8108; it has been noted by GNATS.
From: Manuel Serrano <Manuel.Serrano@sophia.inria.fr>
To: gcc-gnats@gcc.gnu.org, nobody@gcc.gnu.org
Cc:
Subject: Re: c/8108: Problem in the code generator for C and the linker is extremelly slow
Date: 25 Oct 2002 09:00:52 +0200
Hello there,
Somtime ago I have posted a bug report of gcc3.2 and I have received the
following:
> Thank you very much for your problem report.
> It has the internal identification `c/8108'.
> The individual assigned to look at your
> report is: unassigned.
>
> >Category: c
> >Responsible: unassigned
> >Synopsis: Problem in the code generator for C and the linker is extremelly slow
> >Arrival-Date: Tue Oct 01 08:16:02 PDT 2002
This that time I have made extra experiments with several versions of Linux.
I confirm that the problem comes from gcc3.2. With all the Linux kernels
(2.4.18, 2.4.19, 2.4.20pre11), with all the file systems (ext2, ext3, reiserfs)
I have tested, linking my huge (about 1 million lines of C code) last about
a couple of seconds with gcc2.95 and gcc2.96 while it last about 40 minutes
with gcc3.2. Are you aware of this problem? Do you think that it will be fixed
for the next version of gcc?
Many thanks in advance.
--
Manuel
next reply other threads:[~2002-10-25 7:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-25 0:16 Manuel Serrano [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-01-08 14:36 Wolfgang Bangerth
2003-01-08 14:27 bangerth
2003-01-08 2:33 bangerth
2002-10-01 8:16 Manuel.Serrano
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=20021025071602.18181.qmail@sources.redhat.com \
--to=manuel.serrano@sophia.inria.fr \
--cc=gcc-prs@gcc.gnu.org \
--cc=nobody@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).