From: Ian Lance Taylor <iant@google.com>
To: David Brown <david.brown@hesbynett.no>
Cc: "Владимир Андреев" <volodya@netfolder.ru>, gcc-help@gcc.gnu.org
Subject: Re: Structure layout in big/little endian modes
Date: Mon, 28 Nov 2011 10:23:00 -0000 [thread overview]
Message-ID: <mcrobvy7r35.fsf@dhcp-172-18-216-180.mtv.corp.google.com> (raw)
In-Reply-To: <4ED115A0.8040301@hesbynett.no> (David Brown's message of "Sat, 26 Nov 2011 17:36:48 +0100")
David Brown <david.brown@hesbynett.no> writes:
> Do you think it makes sense to file the enhancement request as I
> described in my post, or is it better to discuss it more in the
> mailing lists (either this one, or the gcc development list)? It's a
> feature I'd like to see implemented, but I don't want to clutter the
> bugzilla with a request if you think it is highly unlikely to be
> implemented -
> then it just wastes time for everyone.
As with all gcc enhancements, the best way to make it happen is to do it
yourself. I think that if somebody produced a clean patch for this
functionality, it would be accepted. But it's true that it wouldn't
hurt to raise it on the mailing list to see if somebody is strongly
opposed to it.
> And for filing a request,
> would you prefer me to give a suggestion for the syntax and the effect
> it would have, or is it better to leave it open until someone
> interested in implementing it forms an opinion?
It helps to have a suggestion for the syntax.
Ian
next prev parent reply other threads:[~2011-11-26 17:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-23 21:31 Владимир Андреев
2011-11-23 22:10 ` Ian Lance Taylor
2011-11-24 8:00 ` Paweł Sikora
2011-11-24 12:31 ` David Brown
2011-11-26 17:04 ` Владимир Андреев
2011-11-26 17:23 ` Ian Lance Taylor
2011-11-27 5:20 ` David Brown
2011-11-27 21:25 ` David Brown
2011-11-28 10:23 ` Ian Lance Taylor [this message]
2011-11-28 13:30 ` Владимир Андреев
[not found] <CAJXPUY+H_iS7=iRdxiF+JS0iycJV7d12XK3+1k=NU69=D0se_A@mail.gmail.com>
2011-11-24 8:09 ` Ian Lance Taylor
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=mcrobvy7r35.fsf@dhcp-172-18-216-180.mtv.corp.google.com \
--to=iant@google.com \
--cc=david.brown@hesbynett.no \
--cc=gcc-help@gcc.gnu.org \
--cc=volodya@netfolder.ru \
/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).