Re: update_version_svn (was: Minimum required GNAT version for bootstrap of GNAT on gcc trunk)

2009-04-04 Thread Daniel Berlin
On Sat, Apr 4, 2009 at 2:57 PM, Gerald Pfeifer wrote: > On Tue, 24 Feb 2009, Joseph S. Myers wrote: >> build.html was missing group write permission: >> >> -rw-r--r--   1 gerald   gcc 18920 Mar 30  2008 build.html >> >> This probably meant that the nightly onlinedocs update would fail to >> update

update_version_svn (was: Minimum required GNAT version for bootstrap of GNAT on gcc trunk)

2009-04-04 Thread Gerald Pfeifer
On Tue, 24 Feb 2009, Joseph S. Myers wrote: > build.html was missing group write permission: > > -rw-r--r-- 1 gerald gcc 18920 Mar 30 2008 build.html > > This probably meant that the nightly onlinedocs update would fail to > update it. I've now moved and copied the file so it now has group

Re: Fwd: gcc-4.2-20090304 is now available

2009-04-04 Thread Gerald Pfeifer
On Thu, 5 Mar 2009, H.J. Lu wrote: >>> Maybe we can remove DATESTAMP and updating it now that >>> gcc_update understands to extract the SVN revision number? >> Anyway, removing DATESTAMP would change the issue to new snapshots with no >> changes rather than with just DATESTAMP changes. > My regress

Re: fwprop and CSE const anchor opt

2009-04-04 Thread Adam Nemet
Richard Sandiford writes: > Adam Nemet writes: > > In order for my CSE const anchor patch to work I needed to drastically lower > > the cost of immediate addition in the MIPS backend. This was acceptable as > > a > > proof of concept but not in general of course. > > > > The problem is with "sin

[SOLVED] Re: Is the testsuite broken or did I get the RUNTESTFLAGS syntax wrong?

2009-04-04 Thread Dave Korn
Dave Korn wrote: > I thought this syntax, issued in $objdir > > make -k check-gcc RUNTESTFLAGS="-all gcc.dg/dg.exp=c99-stdint-*" > > would only run testcases that matched the pattern after the equals sign, but > right now on trunk for me it's running everything in gcc.dg/dg.exp: It turns ou

Re: typo in gcc-4.4 changes

2009-04-04 Thread Jonathan Wakely
I spotted some problems in the gcc-4.4/porting_to.html page. There's a missing html entity, the typo "memmber", and multibyte UTF-8 quotes, which are a problem because the web server automatically adds a header specifying Latin1 encoding. I'll commit this patch soon if noone objects. There is cur

Re: Patch for mingw stdint information

2009-04-04 Thread Dave Korn
Kai Tietz wrote: > 2009/4/4 Danny Smith : >> in "mingw-stdint.h" for sanity reason. I will need Kai's help on 32/64 >> bit #ifdefs > Thanks for the patch. Are those defines really just for default target > necessary? Shouldn't be the defines target dependent? Something like > '#define UINTPTR_T

Re: Call for testers: MPC-0.6 released

2009-04-04 Thread Andreas Tobler
Andreas Tobler wrote: Kaveh R. Ghazi wrote: And report your results along with the versions of target triplet/compiler/gmp/mpfr that you used. I've cc'ed others who have access to the platforms in question based on GCC test results. Please help if you can. - powerpc-apple-darwin9.6.0 gcc-4

Re: typo in gcc-4.4 changes

2009-04-04 Thread Richard Sandiford
Pierce Lopez writes: > I was just reading this page: http://gcc.gnu.org/gcc-4.4/changes.html > May I humbly draw your attention to this bullet point: > > -Wparentheses now warns about expressions such as (!x | y) and (!x & > y). Using explicit parentheses, such as in ((!x) | y)), silences this > w

Re: fwprop and CSE const anchor opt

2009-04-04 Thread Richard Sandiford
Adam Nemet writes: > In order for my CSE const anchor patch to work I needed to drastically lower > the cost of immediate addition in the MIPS backend. This was acceptable as a > proof of concept but not in general of course. > > The problem is with "single-insn"/simple constants. We would also

Re: Patch for mingw stdint information

2009-04-04 Thread Kai Tietz
2009/4/4 Danny Smith : >> Hi all, >> >> Please find attached a patch I built to add stdint-related >> information >> to GCC configuration for the mingw target (see >> http://gcc.gnu.org/ml/gcc/2009-04/msg0.html >>   for more details about why). > > Thanks for this.  I am just in the process of