public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: DJ Delorie <dj@redhat.com>
To: Mark Mitchell <mark@codesourcery.com>
Cc: iant@google.com, gcc@gcc.gnu.org
Subject: Re: bitfields: types vs modes?
Date: Tue, 14 Jul 2009 20:12:00 -0000	[thread overview]
Message-ID: <200907142010.n6EKAWVR013169@greed.delorie.com> (raw)
In-Reply-To: <4A14EE51.6010804@codesourcery.com> (message from Mark Mitchell 	on Wed, 20 May 2009 23:01:53 -0700)


> >> I think the ARM specification is pretty sensible, and would make a
> >>  good cross-platform approach.
> > 
> > Could you distill it for us? 
> 
> The relevant bits are from AAPCS \S 7.1.7.5, and quoted below.

I finally got the last of the feedback I needed from our customers,
and they agree that the AAPCS functionality is suitable for their
ports as well.

What's the next step?

  reply	other threads:[~2009-07-14 20:12 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-10  8:18 DJ Delorie
2009-03-11  7:36 ` Hans-Peter Nilsson
2009-03-11  7:42   ` DJ Delorie
2009-03-11 13:24     ` Laurent GUERBY
2009-03-11 11:57 ` Paul Brook
2009-03-11 13:55   ` Hans-Peter Nilsson
2009-04-01  5:11 ` DJ Delorie
2009-04-01  5:33   ` Ian Lance Taylor
2009-04-06 17:20     ` Mark Mitchell
2009-04-06 20:11       ` DJ Delorie
2009-04-06 20:46         ` Mark Mitchell
2009-05-20 21:35           ` DJ Delorie
2009-05-20 21:48             ` Ian Lance Taylor
2009-05-20 22:10               ` Mark Mitchell
2009-05-21  1:34                 ` DJ Delorie
2009-05-21 11:51                   ` Mark Mitchell
2009-07-14 20:12                     ` DJ Delorie [this message]
2009-07-15  1:09                       ` Mark Mitchell
2009-07-15  1:15                         ` DJ Delorie
2009-07-16 23:19                         ` DJ Delorie

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=200907142010.n6EKAWVR013169@greed.delorie.com \
    --to=dj@redhat.com \
    --cc=gcc@gcc.gnu.org \
    --cc=iant@google.com \
    --cc=mark@codesourcery.com \
    /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).