From: "andrzej zaborowski" <balrogg@gmail.com>
To: ananaza@iki.fi, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Re: gcc
Date: Tue, 4 Dec 2007 23:10:05 +0100 [thread overview]
Message-ID: <fb249edb0712041410n6cca0756g72ee60b1270dff39@mail.gmail.com> (raw)
In-Reply-To: <87zlwqw3bu.fsf@brigitte.dna.fi>
On 04/12/2007, Antti P Miettinen <ananaza@iki.fi> wrote:
> Rick Vernam <rickv@hobi.com> writes:
> > any comments on the current status of moving beyond dependency on GCC 3.3.6?
>
> Sorry for a vague ignorant question, but would the gcc-4 issues be
> affected in any way if the ops were inside a big function (use labels
> to find them) vs the current use of separate functions?
They might likely be affected but it would be an equally fragile and
compiler-dependent solution and I think not worth putting the time it
would take to adapt dyngen to this.
Regards
next prev parent reply other threads:[~2007-12-04 22:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-04 2:20 [Qemu-devel] gcc Rick Vernam
2007-12-04 21:35 ` [Qemu-devel] gcc Antti P Miettinen
2007-12-04 22:10 ` andrzej zaborowski [this message]
2007-12-04 22:17 ` Johannes Schindelin
2007-12-04 22:26 ` Johannes Schindelin
2007-12-05 0:35 ` [Qemu-devel] gcc Carlo Marcelo Arenas Belon
2007-12-05 15:41 ` Rick Vernam
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=fb249edb0712041410n6cca0756g72ee60b1270dff39@mail.gmail.com \
--to=balrogg@gmail.com \
--cc=ananaza@iki.fi \
--cc=qemu-devel@nongnu.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 NNTP newsgroup(s).