Re: [PATCH 2/4] Docs: extend.texi: Remove trailing blanks from lines

2011-05-04 Thread Mike Stump
On May 4, 2011, at 11:46 AM, Joseph S. Myers wrote: I explicitly approve trailing whitespace removal from all .texi files and other documentation not imported from upstream sources outside of GCC (subject to handling generated files properly, so any changes to tm.texi should be done by

Re: [PATCH 2/4] Docs: extend.texi: Remove trailing blanks from lines

2011-05-04 Thread Mike Stump
On May 4, 2011, at 11:40 AM, Gerald Pfeifer wrote: Documentation may be a bit more relaxed, and if you have one doc maintainer approve and the other abstain that may be more boring that you might hope for. :-) Actually, I was aiming for a global person to ack gcc/*... This could be less

[PATCH] don't use build_function_type in the ObjC/C++ frontends

2011-05-04 Thread Nathan Froyd
The last remaining uses of build_function_type in the ObjC/C++ frontends comes from this pattern: tree method_param_types = get_arg_type_list (method_prototype, METHOD_REF, super_flag); tree ftype = build_function_type (ret_type, method_param_types); To eliminate this, I made the

Go patch committed: Use backend interface for slice types

2011-05-04 Thread Ian Lance Taylor
This patch to the Go frontend uses the backend interface for slice types. Bootstrapped and ran Go testsuite on x86_64-unknown-linux-gnu. Committed to mainline. Ian diff -r 37dae2a9c21b go/gogo-tree.cc --- a/go/gogo-tree.cc Wed May 04 08:38:47 2011 -0700 +++ b/go/gogo-tree.cc Wed May 04 22:18:22

[google] improves option mismatch handling for LIPO (issue4479045)

2011-05-04 Thread David Li
This patch improves cross module option mismatch handling in LIPO mode -- will be commited to google/main. 1) Remove duplicates in the option list before comparison; 2) Force module incompatiblity when two modules disagree in -fexceptions setting. In LIPO mode, when option mismatch is

[Patch, Fortran] -std=f2008tr, TR 29113 and OPTIONAL arguments with BIND(C)

2011-05-04 Thread Tobias Burnus
This patch does the first minor steps towards TR 29113: It accepts the OPTIONAL attribute in procedures with C binding. As gfortran already passes absent arguments a NULL pointer, there is no changed needed, except in the diagnostics part. Additionally, it is a feature also supported by other

<    1   2