Re: gcc --help for options which are not warnings or optimizations

Hi Ian, Nick, how is gcc --help supposed to work for options which are neither warnings nor optimizations? For example, -fstack-protector. Is there a --help option which will display it? Yes - but only the generic "--help --verbose" rather than a more qualified version. My original goal w

Re: Inner loop unable to compute sufficient information during vectorization

Abhishek Shrivastav wrote on 31/05/2009 16:44:34: > In this case, I think that Outer loop could be vectorized as there is > no dependency in the loop,the access pattern is simple enough and > there is unit stride in both the loops. Current version 4.4.* is not > doing outer loop vectorization.

Re: gcc --help for options which are not warnings or optimizations

On Tue, Jun 2, 2009 at 05:38, Nick Clifton wrote: > I suppose we could add another qualifier along the lines of > "--help=not-otherwise-shown" but that seems rather klunky. --help=other? (I've got tons of other colors for this bike shed, if needed). Diego.

Enquiry

Dear Sir, I am using gcc compiler for v850e cpu. When I use the arrtribute: __attribute__ ((interrupt_handler)) or __attribute__ ((interrupt); for interrupt function, say for example void swnmi() __attribute__ ((interrupt_handler)); void swnmi() { ... .. } main() { .. .. } I am g

Re: gcc --help for options which are not warnings or optimizations

Nick Clifton writes: > Hi Ian, > >> Nick, how is gcc --help supposed to work for options which are neither >> warnings nor optimizations? For example, -fstack-protector. Is there a >> --help option which will display it? > > Yes - but only the generic "--help --verbose" rather than a more > qua

Enquiry

Dear Sir, I am using gcc compiler for v850e cpu. When I use the arrtribute: __attribute__ ((interrupt_handler)) or __attribute__ ((interrupt); for interrupt function, say for example void swnmi() __attribute__ ((interrupt_handler)); void swnmi() { ... .. } main() { .. .. } I am get

[lto] Merged with mainline @147915

Thanks to Jan for doing most of this merge. This brings the new inliner heuristics and clone framework into the branch. Jan still has some fallout to fix, so I've disabled gcc.dg/ipa/ipa.exp for now. I also need to fix a few tests in libstdc++, which are better fixed with the new streamer code.

Re: RFC: Option handling and PR 37565

On Fri, May 29, 2009 at 09:02:23AM -0700, Steve Ellcey wrote: > While looking into PR 37565 I began to wonder if we need to modify how > we handle optimization flag handling. Currently we have > OVERRIDE_OPTIONS, C_COMMON_OVERRIDE_OPTIONS, and OPTIMIZATION_OPTIONS to > set or override the optimiza

gcc-4.4-20090602 is now available

Snapshot gcc-4.4-20090602 is now available on ftp://gcc.gnu.org/pub/gcc/snapshots/4.4-20090602/ and on various mirrors, see http://gcc.gnu.org/mirrors.html for details. This snapshot has been generated from the GCC 4.4 SVN branch with the following options: svn://gcc.gnu.org/svn/gcc/branches

Information

Hi Dearest. I will like to invest in your country,I will like to know the proceedings of a non-Citizen investing in your country? Actually I am contacting you ‘outstanding that l cannot invest in your country without an assistant from someone from your country. Factually I want you

question about TARGET_MUST_PASS_IN_STACK

On xstormy16, when structures with variable-length arrays are passed to functions (execute/20020412-1.c), it appears that they're passed by reference (based on examining the stack), despite the port not explicitly requesting that. This causes a mis-match in the va_arg code, which assumes the arra