From: Ulrich Weigand <Ulrich.Weigand@de.ibm.com>
To: dnovillo@google.com (Diego Novillo)
Cc: joern.rennecke@embecosm.com, nathan@codesourcery.com,
gingold@adacore.com, nickc@redhat.com, dje.gcc@gmail.com,
law@redhat.com, rdsandiford@googlemail.com, dj@redhat.com,
wilson@tuliptree.org, rth@redhat.com, echristo@gmail.com,
gcc-patches@gcc.gnu.org
Subject: Re: VEC re-write [patch 01/25]
Date: Tue, 20 Nov 2012 13:57:00 -0000 [thread overview]
Message-ID: <OFBE5C1414.426ACF61-ONC1257ABC.004C5C7F-C1257ABC.004CA18A@de.ibm.com> (raw)
In-Reply-To: <CAD_=9DT4z=7Vp5g7JYkqzWWFTK5h7mom9Ys98HwGaXoZQhcowQ@mail.gmail.com> from "Diego Novillo" at Nov 17, 2012 09:57:07 PM
Diego Novillo wrote:
> On Thu, Nov 15, 2012 at 4:53 PM, Diego Novillo <dnovillo@google.com> wrote:
>
> > I have tested the patch pretty extensively:
> >
> > - Regular bootstraps on x86_64, ppc, ia64, sparc and hppa.
> > - Bootstraps with --enable-checking=release
> > - Bootstraps with --enable-checking=gc,gcac
> > - Basic builds on all targets (using contrib/config-list.mk).
>
> I have now committed all 25 parts of this patch as rev 193595. Please
> CC me on any problems that you think may be related to this rewrite.
This breaks an spu-elf cross-compiler built on a powerpc64-linux host
using a gcc 4.1.2 host compiler (i.e. RHEL5.x, which is the latest RHEL
distro that still supports running on Cell/B.E.).
I'm getting errors along the lines of:
/home/uweigand/fsf/gcc-head/gcc/tree-data-ref.c: In function 'conflict_function* conflict_fn(unsigned int, ...)':
/home/uweigand/fsf/gcc-head/gcc/tree-data-ref.c:1599: warning: cannot receive objects of non-POD type 'class affine_fn' through '...'; call will abort at runtime
And indeed it does then abort at runtime when building libgfortran
(with -ftree-vectorize enabled).
"affine_fn" is defined in tree-data-ref.h as:
typedef vec<tree> affine_fn;
which apparently is no longer a POD type?
Bye,
Ulrich
--
Dr. Ulrich Weigand
GNU Toolchain for Linux on System z and Cell BE
Ulrich.Weigand@de.ibm.com
next prev parent reply other threads:[~2012-11-20 13:57 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-15 21:53 Diego Novillo
[not found] ` <50A61414.8070908@redhat.com>
2012-11-16 12:13 ` Diego Novillo
2012-11-16 12:22 ` Pedro Alves
2012-11-16 23:16 ` Ian Lance Taylor
2012-11-18 2:57 ` Diego Novillo
2012-11-18 17:05 ` Hans-Peter Nilsson
2012-11-18 17:12 ` Diego Novillo
2012-11-18 17:43 ` Hans-Peter Nilsson
2012-11-18 17:48 ` Diego Novillo
2012-11-18 19:15 ` Andrew Pinski
2012-11-19 19:57 ` Jack Howarth
2012-11-19 20:16 ` Jack Howarth
2012-11-25 13:11 ` Richard Biener
2012-11-25 15:25 ` Diego Novillo
2012-11-18 18:25 ` Andreas Tobler
2012-11-18 19:12 ` Hans-Peter Nilsson
2012-11-18 19:32 ` Andreas Tobler
2012-11-18 19:50 ` Hans-Peter Nilsson
2012-11-20 13:57 ` Ulrich Weigand [this message]
2012-11-18 21:28 David Edelsohn
2012-11-19 1:04 ` Diego Novillo
2012-11-19 1:14 ` David Edelsohn
2012-11-19 3:18 ` Ian Lance Taylor
2012-11-19 14:46 ` 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=OFBE5C1414.426ACF61-ONC1257ABC.004C5C7F-C1257ABC.004CA18A@de.ibm.com \
--to=ulrich.weigand@de.ibm.com \
--cc=dj@redhat.com \
--cc=dje.gcc@gmail.com \
--cc=dnovillo@google.com \
--cc=echristo@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gingold@adacore.com \
--cc=joern.rennecke@embecosm.com \
--cc=law@redhat.com \
--cc=nathan@codesourcery.com \
--cc=nickc@redhat.com \
--cc=rdsandiford@googlemail.com \
--cc=rth@redhat.com \
--cc=wilson@tuliptree.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).