public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Michael Meissner <meissner@linux.vnet.ibm.com>
To: David Edelsohn <dje.gcc@gmail.com>
Cc: Michael Meissner <meissner@linux.vnet.ibm.com>,
	gcc-patches@gcc.gnu.org,         Jakub Jelinek <jakub@redhat.com>
Subject: Re: [PATCH] Fix builtin attributes on powerpc
Date: Tue, 13 Oct 2009 20:40:00 -0000	[thread overview]
Message-ID: <20091013202500.GA9438@hungry-tiger.westford.ibm.com> (raw)
In-Reply-To: <303e1d290910130630v33b0fe11sd59a5a806b4eb948@mail.gmail.com>

On Tue, Oct 13, 2009 at 09:30:28AM -0400, David Edelsohn wrote:
> On Thu, Oct 1, 2009 at 2:57 PM, Michael Meissner
> <meissner@linux.vnet.ibm.com> wrote:
> > I tried to get this in by yesterday, but I had some server issues, and I
> > couldn't get the tests run until today.
> >
> > In working with Jakub on a backport of the power7 patches to the Red Hat 4.4
> > branch, we found some problems in running spec.  The problem turned out to that
> > the vectorized math functions had different declaration attributes than the
> > scalar versions of the functions.  In doing further investigation, it turned
> > out that we weren't setting any attributes for any builtin functions.  This
> > patch fixes the attributes for the Altivec (VMX) and VSX builtins.  I have not
> > done the spe and paired builtins in this patch, but that can be easily done
> > later.
> >
> > I did the usual boostrap and make check with no regressions.
> >
> > Is this acceptable to checkin under stage 3 as a backend change?
> 
> If this is the design that the community wants to use in all backends,
> it is fine with me.

It is too late for GCC 4.5 to do things in a common fashion.  The real solution
is to move the backend builtins into the main builtins.  I had some patches to
allow backends to optionally do this, and when 4.6 opens up we can explore
this.

However, I'm trying to fix the problem right now, and so this particular
solution is limited to just to tie the definition of the builtin enum and flags
together in one place, rather than having a separate switch statement that is
problematical, because you have to edit stuff in multiple places.  We already
have the problem between the rs6000.h, rs6000.c, and rs6000-c.c files that each
have some knowledge of builtins (and overloaded builtins make it even worse).

> I think MAX_RS6000_BUILTINS is more consistent with the naming
> convention in the rest of GCC than RS6000_BUILTIN_COUNT.

I agree MAX_RS6000_BUILTINS is more consistant, but RS6000_BUILTIN_COUNT is
what was originally used, so I didn't change that.

> The patch is okay.

Ok.

-- 
Michael Meissner, IBM
4 Technology Place Drive, MS 2203A, Westford, MA, 01886, USA
meissner@linux.vnet.ibm.com

  reply	other threads:[~2009-10-13 20:30 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-01 18:58 Michael Meissner
2009-10-01 19:01 ` Andrew Pinski
2009-10-01 19:14   ` Michael Meissner
2009-10-13 13:36 ` David Edelsohn
2009-10-13 20:40   ` Michael Meissner [this message]
2009-10-14  0:02     ` David Edelsohn
2009-10-14  9:58       ` Richard Guenther
2009-10-14 15:21       ` Michael Meissner
2009-10-14 16:19         ` Richard Guenther
2009-10-14 20:08         ` David Edelsohn
2009-10-14 22:21           ` Michael Meissner
2009-10-15 20:59           ` [PATCH, committed] PR target/23983, fix " Michael Meissner
2009-10-19 22:24             ` Jakub Jelinek
2009-10-20 16:29               ` Jakub Jelinek
2009-10-20 17:56                 ` David Edelsohn

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=20091013202500.GA9438@hungry-tiger.westford.ibm.com \
    --to=meissner@linux.vnet.ibm.com \
    --cc=dje.gcc@gmail.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jakub@redhat.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).