From: ron minnich <rminnich@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] c compiler bug
Date: Tue, 14 Sep 2010 14:07:58 -0700 [thread overview]
Message-ID: <AANLkTimNkC82UhS4aUqQd1ewEjxUp5AG5BpAFz4VBrgM@mail.gmail.com> (raw)
In-Reply-To: <8593B51E-E9F9-4E68-BC24-DDC951362A5C@coraid.com>
On Tue, Sep 14, 2010 at 1:59 PM, Brantley Coile <brantley@coraid.com> wrote:
> I've a need for the pragma. We're using it. That's how I found the problem.
> bwc
I can tell you that people who use this sort of thing at some point
discover it's not really what they wanted. They end up writing
functions to more or less do the same thing. I'm not sure you want to
go down this path.
Example: Xen 2 used __attribute__ packed heavily, realized at some
point it was a bad idea, and took another path.
ron
next prev parent reply other threads:[~2010-09-14 21:07 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-14 15:25 erik quanstrom
2010-09-14 20:20 ` Charles Forsyth
2010-09-14 20:59 ` Brantley Coile
2010-09-14 21:07 ` ron minnich [this message]
2010-09-15 7:06 ` Sape Mullender
2010-09-15 8:30 ` Charles Forsyth
2010-09-15 8:37 ` Charles Forsyth
2010-09-15 12:20 ` Charles Forsyth
2010-09-15 8:32 ` Charles Forsyth
2013-02-17 2:38 erik quanstrom
2013-02-18 13:02 ` Comeau At9Fans
2013-02-18 14:38 ` Charles Forsyth
2013-02-18 15:02 ` erik quanstrom
2013-02-18 15:10 ` Charles Forsyth
2013-02-21 17:17 ` Comeau At9Fans
2013-02-21 17:13 ` Comeau At9Fans
2013-02-21 18:13 ` hiro
2013-02-21 18:22 ` John Floren
2013-02-21 18:39 ` erik quanstrom
2013-02-21 18:46 ` Comeau At9Fans
2013-02-21 18:51 ` John Floren
2013-02-21 19:36 ` hiro
2013-02-21 19:58 ` andrey mirtchovski
2013-02-21 20:24 ` Matthew Veety
2013-02-21 20:27 ` David Leimbach
2013-02-21 20:36 ` steve
2013-02-21 18:51 ` Kurt H Maier
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=AANLkTimNkC82UhS4aUqQd1ewEjxUp5AG5BpAFz4VBrgM@mail.gmail.com \
--to=rminnich@gmail.com \
--cc=9fans@9fans.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;
as well as URLs for NNTP newsgroup(s).