From: Nix <nix@esperi.org.uk>
To: BlaisorBlade <blaisorblade_spam@yahoo.it>
Cc: user-mode-linux-devel@lists.sourceforge.net,
Jeff Dike <jdike@addtoit.com>
Subject: Re: [uml-devel] [patch 1/1] Avoid that gcc breaks UML with "unit at a time" compilation mode.
Date: Wed, 23 Jun 2004 17:14:46 +0100 [thread overview]
Message-ID: <87k6xynte1.fsf@amaterasu.srvr.nix> (raw)
In-Reply-To: <200406191247.19316.blaisorblade_work@yahoo.it> (BlaisorBlade's message of "Sat, 19 Jun 2004 12:47:48 +0200")
On Sat, 19 Jun 2004, BlaisorBlade mused:
> Avoid that gcc breaks UML with "unit at a time" compilation mode; this patch
> is for 2.6. Please test it.
btw, I'd call this a workaround. Only a very few files --- that depend on
the exact ordering of functions, variable declarations, or top-level asm
blocks in the file --- should need it.
Eventually, non-unit-at-a-time mode will probably go away entirely.
--
`We in no way believe that this Christ was a space alien.'
--- A creationist website goes completely bonkers
-------------------------------------------------------
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 -
digital self defense, top technical experts, no vendor pitches,
unmatched networking opportunities. Visit www.blackhat.com
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
prev parent reply other threads:[~2004-06-23 16:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-19 10:47 [uml-devel] [patch 1/1] Avoid that gcc breaks UML with "unit at a time" compilation mode BlaisorBlade
2004-06-23 16:14 ` Nix [this message]
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=87k6xynte1.fsf@amaterasu.srvr.nix \
--to=nix@esperi.org.uk \
--cc=blaisorblade_spam@yahoo.it \
--cc=jdike@addtoit.com \
--cc=user-mode-linux-devel@lists.sourceforge.net \
/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