From: Andrew Pinski <pinskia@physics.uc.edu>
To: Karel Gardas <kgardas@objectsecurity.com>
Cc: gcc@gcc.gnu.org
Subject: Re: [pch-branch] missing binary operator issue.
Date: Thu, 02 Jan 2003 22:21:00 -0000 [thread overview]
Message-ID: <6E630445-1EA0-11D7-9553-00039372607E@physics.uc.edu> (raw)
In-Reply-To: <Pine.LNX.4.43.0301022219220.7028-100000@thinkpad.c0202001.roe.itnq.net>
On Thursday, Jan 2, 2003, at 13:25 US/Pacific, Karel Gardas wrote:
> BTW: IMHO something strage is with my gcc3.4-pch... the branch compiled
> 10-20 % slower than version which I tried before, and whole
> configuration
> process seems to be moved to build process. Is this behaviour right, or
> have I done something wrong?
This is because 3.4 changed how every thing is done with building gcc,
It was done
so to autoconfive the top-level configure and Makefile.
Thanks,
Andrew Pinski
next prev parent reply other threads:[~2003-01-02 22:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-13 4:04 Karel Gardas
2003-01-02 17:59 ` Geoff Keating
2003-01-02 21:26 ` Karel Gardas
2003-01-02 22:21 ` Andrew Pinski [this message]
2003-01-07 19:32 ` Geoff Keating
2003-01-08 16:06 ` Karel Gardas
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=6E630445-1EA0-11D7-9553-00039372607E@physics.uc.edu \
--to=pinskia@physics.uc.edu \
--cc=gcc@gcc.gnu.org \
--cc=kgardas@objectsecurity.com \
/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).