public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: rth@gcc.gnu.org
To: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, hzoli@hzoli.2y.net,
nobody@gcc.gnu.org, rth@gcc.gnu.org
Subject: Re: c/10675: Compile time increases quadratically with struct size
Date: Fri, 09 May 2003 01:25:00 -0000 [thread overview]
Message-ID: <20030509012535.29965.qmail@sources.redhat.com> (raw)
Synopsis: Compile time increases quadratically with struct size
Responsible-Changed-From-To: unassigned->rth
Responsible-Changed-By: rth
Responsible-Changed-When: Fri May 9 01:25:35 2003
Responsible-Changed-Why:
Patch in progress.
http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=10675
next reply other threads:[~2003-05-09 1:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-09 1:25 rth [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-05-12 22:26 Richard Henderson
2003-05-12 22:16 Zoltan Hidvegi
2003-05-12 3:32 rth
2003-05-08 22:34 ehrhardt
2003-05-08 1:56 hzoli
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=20030509012535.29965.qmail@sources.redhat.com \
--to=rth@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.org \
--cc=gcc-gnats@gcc.gnu.org \
--cc=gcc-prs@gcc.gnu.org \
--cc=hzoli@hzoli.2y.net \
--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).