From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] 8c "out of fixed registers"
Date: Mon, 19 Nov 2007 17:05:00 -0500 [thread overview]
Message-ID: <45f342ca991ac51d3dcf47fd98dd7aa7@quanstro.net> (raw)
In-Reply-To: <4741DA7C.6040304@gmail.com>
> Charles Forsyth wrote:
> > yes, that's the sort of thing that will do it.
> > the resulting expressions are pointlessly big,
> > with lots of parentheses to reduce ordering options.
>
> And yet, other "inferior" compilers like gcc can build it. Sorry, I'm a
> bit jaded by all the gcc/linux bashing on this list. This isn't
> necessarily aimed at Charles, more at the list.
not sure how one bug that only manifests on code that
deserves to loose (have you read it?) makes 8c worse than gcc.
- erik
next prev parent reply other threads:[~2007-11-19 22:05 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-19 4:12 Federico G. Benavento
2007-11-19 9:32 ` [9fans] Fwd: " Federico Benavento
2007-11-19 17:45 ` [9fans] " erik quanstrom
2007-11-19 18:14 ` Charles Forsyth
2007-11-19 18:13 ` Federico G. Benavento
2007-11-19 18:37 ` Charles Forsyth
2007-11-19 18:48 ` Robert William Fuller
2007-11-19 19:14 ` Charles Forsyth
2007-11-19 19:21 ` Charles Forsyth
2007-11-19 20:38 ` Uriel
2007-11-19 21:08 ` Iruata Souza
2007-11-20 0:20 ` dave.l
2007-11-20 3:54 ` Bruce Ellis
2007-11-20 15:28 ` Iruata Souza
2007-11-20 16:39 ` David Leimbach
2007-11-20 16:48 ` Iruata Souza
2007-11-20 17:05 ` David Leimbach
2007-11-20 17:29 ` Anthony Sorace
2007-11-22 10:17 ` Douglas A. Gwyn
2007-11-22 12:24 ` erik quanstrom
2007-11-20 22:58 ` dave.l
2007-11-21 1:11 ` Iruata Souza
2007-11-20 22:58 ` dave.l
2007-11-21 16:15 ` Uriel
2007-11-26 10:30 ` Douglas A. Gwyn
2007-11-19 22:05 ` erik quanstrom [this message]
2007-11-19 20:00 ` Bruce Ellis
2007-11-19 22:18 ` Charles Forsyth
2007-11-19 18:18 ` Charles Forsyth
2007-11-19 18:32 ` Federico G. Benavento
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=45f342ca991ac51d3dcf47fd98dd7aa7@quanstro.net \
--to=quanstro@quanstro.net \
--cc=9fans@cse.psu.edu \
/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 NNTP newsgroup(s).