Re: RFC: Hack to make restrict more useful

2007-09-01 Thread Richard Guenther
On 9/1/07, Mark Mitchell <[EMAIL PROTECTED]> wrote: > This bug: > > http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33272 > > is about a situation in which -fargument-noalias works better than > putting "restrict" on all pointer arguments to a function, even though > that should be logically equivalent

Build failure on Darwin, revision 127998 (solved)

2007-09-01 Thread Dominique Dhumieres
Following http://gcc.gnu.org/ml/gcc/2007-08/msg00544.html I have updated to revision 128003 and tried 'make bootstrap', then 'configure' + 'make bootstrap' without success (the same kind of failure in libgcc). I the tried a fresh install: new directory, configure, and make, and it worked. So now

GCC Plugin Branch

2007-09-01 Thread Brendon Costa
Hi all, I have just recently had time to checkout and build the GCC plugin branch. I am interested in building a simple plugin to give it a try. After reading through the patches it seems simple enough, I just need to create a shared library that defines the symbols: pre_translation_unit transfor

Re: RFC: Hack to make restrict more useful

2007-09-01 Thread Mark Mitchell
Richard Guenther wrote: >> I have a prototype hack which changes checks of flag_argument_noalias != >> 0 to also check for the presence of "restrict" on all pointer arguments. >> This fixes the test case, modulo a C front-end bug which Joseph has >> volunteered to fix. > AFAIK Danny had been "fi

(gcc 4.2) how to create an ADDR_EXPR that refers to a linkage name?

2007-09-01 Thread Gary Funck
We are in the process of updating GCC/UPC's support for the UPC dialect of C to version 4.2.0 of GCC. GCC/UPC is described here: http://www.intrepid.com/upc.html Generally, things are working. However, at the moment, all tests fail when optimizations are enabled. For example: test00.upc:35: inte

Re: (gcc 4.2) how to create an ADDR_EXPR that refers to a linkage name?

2007-09-01 Thread Diego Novillo
On 9/1/07, Gary Funck <[EMAIL PROTECTED]> wrote: > All suggestions/help appreciated, - Gary Have you considered using the data sharing machinery in OpenMP? We simply create a data structure holding all shared variables, allocate that in shared memory and re-write all references to shared variabl

Re: (gcc 4.2) how to create an ADDR_EXPR that refers to a linkage name?

2007-09-01 Thread Gary Funck
On Sat, Sep 01, 2007 at 01:43:37PM -0400, Diego Novillo wrote: > > Have you considered using the data sharing machinery in OpenMP? We > simply create a data structure holding all shared variables, allocate > that in shared memory and re-write all references to shared variables > as dereferences t

Re: RFC: Hack to make restrict more useful

2007-09-01 Thread Richard Guenther
On 9/1/07, Mark Mitchell <[EMAIL PROTECTED]> wrote: > Richard Guenther wrote: > > >> I have a prototype hack which changes checks of flag_argument_noalias != > >> 0 to also check for the presence of "restrict" on all pointer arguments. > >> This fixes the test case, modulo a C front-end bug which

Re: RFC: Hack to make restrict more useful

2007-09-01 Thread Mark Mitchell
Richard Guenther wrote: >> I fully concede that my trick isn't a general solution to making full >> use of restrict. But, given that I think it'll take about 20-50 lines >> of code, and that it will get a lot of the common cases, I think it's >> worth it. Do you agree? > > Yes, I agree. I just

Re: RFC: Hack to make restrict more useful

2007-09-01 Thread Mark Mitchell
Richard Guenther wrote: >> OK, great. Here's a draft patch for the trick; this works on the test >> case I had, and I'll be testing it now. If it passes testing, and I add >> testcases, does this look OK to you? Thanks for the speedy and accurate review! >> + bool noalias; > > it's an int.

Re: RFC: Hack to make restrict more useful

2007-09-01 Thread Richard Guenther
On 9/1/07, Mark Mitchell <[EMAIL PROTECTED]> wrote: > Richard Guenther wrote: > > >> I fully concede that my trick isn't a general solution to making full > >> use of restrict. But, given that I think it'll take about 20-50 lines > >> of code, and that it will get a lot of the common cases, I thin