From: Trevor Saunders <tbsaunde@tbsaunde.org>
To: Jakub Jelinek <jakub@redhat.com>
Cc: Andreas Schwab <schwab@linux-m68k.org>, Jeff Law <law@redhat.com>,
tbsaunde+gcc@tbsaunde.org, gcc-patches@gcc.gnu.org
Subject: Re: [PATCH 3/8] add default for PCC_BITFIELD_TYPE_MATTERS
Date: Thu, 30 Apr 2015 13:07:00 -0000 [thread overview]
Message-ID: <20150430124336.GC1508@tsaunders-iceball.corp.tor1.mozilla.com> (raw)
In-Reply-To: <20150430123344.GQ1751@tucnak.redhat.com>
On Thu, Apr 30, 2015 at 02:33:44PM +0200, Jakub Jelinek wrote:
> On Thu, Apr 30, 2015 at 08:25:14AM -0400, Trevor Saunders wrote:
> > On Thu, Apr 30, 2015 at 08:40:50AM +0200, Andreas Schwab wrote:
> > > Trevor Saunders <tbsaunde@tbsaunde.org> writes:
> > >
> > > > actually pointing out libojc/encoding.c was more useful since that makes
> > > > it pretty clear the ifndef PCC_BITFIELD_TYPE_MATTERS there just needs to
> > > > be changed to #if !
> > >
> > > That probably won't work on arm or powerpc or vax:
> > >
> > > gcc/config/arm/arm.h:#define PCC_BITFIELD_TYPE_MATTERS TARGET_AAPCS_BASED
> > > gcc/config/rs6000/sysv4.h:#define PCC_BITFIELD_TYPE_MATTERS (TARGET_BITFIELD_TYPE)
> > > gcc/config/vax/vax.h:#define PCC_BITFIELD_TYPE_MATTERS (! TARGET_VAXC_ALIGNMENT)
> >
> > hrmph, I don't see how this code ever worked correctly on those targets.
> > Consider the arm case the value of PCC_BITFIELD_TYPE_MATTERS depends on
> > arm_abi so if the bitfield type matters depends on what abi libobjc is
> > being built for, but its not obvious how libobjc is dealing with that.
> > I suppose it could be that libobjc is using this macro to know something
> > else that only sort of relaed somehow. Unfortunately this code seems to
> > come from the creation of libobjc/ in 11998 and though the commit says
> > it is a move from gcc/objc/ nothing appears to have been removed from
> > gcc/objc/.
> >
> > I guess the "best" thing to do is justadd a
> > __PCC_BITFIELD_TYPE_MATTERS__ that gcc defines and use that in libobjc?
>
> I think adding way too many predefines, especially rarely used ones, is
> harmful, certainly it isn't free, consider -g3 or -dD where it will all end
> up in, additional gcc start overhead, ...
there was a reason I said "best" I don't think its a great design
either.
> Can't just libobjc configury test for that?
I suppose it can test what happens with alignment of different types in
structs. I guess I'm not really awake yet, and I'm pretty wary of
this since I really have no idea what its trying to do.
Trev
>
> Jakub
next prev parent reply other threads:[~2015-04-30 12:43 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-27 5:56 [PATCH 0/8] remove more conditional compilation tbsaunde+gcc
2015-04-27 5:56 ` [PATCH 3/8] add default for PCC_BITFIELD_TYPE_MATTERS tbsaunde+gcc
2015-04-29 13:18 ` Andreas Schwab
2015-04-29 21:54 ` Trevor Saunders
2015-04-29 22:00 ` Andreas Schwab
2015-04-29 22:26 ` Jeff Law
2015-04-29 22:30 ` Trevor Saunders
2015-04-29 22:33 ` Jeff Law
2015-04-30 1:45 ` Trevor Saunders
2015-04-30 3:24 ` Trevor Saunders
2015-04-30 4:13 ` Jeff Law
2015-04-30 7:13 ` Andreas Schwab
2015-04-30 11:59 ` Trevor Saunders
2015-04-30 12:17 ` Jakub Jelinek
2015-04-30 12:22 ` Andreas Schwab
2015-04-29 22:40 ` Jeff Law
2015-04-30 6:58 ` Andreas Schwab
2015-04-30 12:34 ` Trevor Saunders
2015-04-30 12:39 ` Jakub Jelinek
2015-04-30 13:07 ` Trevor Saunders [this message]
2015-04-30 17:50 ` Joseph Myers
2015-05-01 0:01 ` Trevor Saunders
2015-04-27 5:56 ` [PATCH 1/8] add default for NO_FUNCTION_CSE tbsaunde+gcc
2015-04-27 5:57 ` [PATCH 8/8] remove #if ARGS_GROW_DOWNWARD tbsaunde+gcc
2015-04-27 5:57 ` [PATCH 5/8] always define HAVE_simple_return and HAVE_return tbsaunde+gcc
2015-05-06 1:13 ` Mike Stump
2015-05-06 3:16 ` Trevor Saunders
2015-04-27 5:57 ` [PATCH 2/8] add default for HARD_REGNO_RENAME_OK tbsaunde+gcc
2015-04-27 5:57 ` [PATCH 6/8] always define HAVE_epilogue tbsaunde+gcc
2015-04-27 5:57 ` [PATCH 7/8] always define ARGS_GROW_DOWNWARD tbsaunde+gcc
2015-04-27 5:57 ` [PATCH 4/8] add default for EPILOGUE_USES tbsaunde+gcc
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=20150430124336.GC1508@tsaunders-iceball.corp.tor1.mozilla.com \
--to=tbsaunde@tbsaunde.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=law@redhat.com \
--cc=schwab@linux-m68k.org \
--cc=tbsaunde+gcc@tbsaunde.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 read-only IMAP folder(s) and NNTP newsgroup(s).