Re: Define __attribute__((no_instrument_function)) but still got instrumented

2020-08-06 Thread Richard Biener via Gcc
On Fri, Aug 7, 2020 at 8:35 AM Shuai Wang via Gcc wrote: > > Hello! > > I am working on a ARM GCC plugin which instruments each GIMPLE function > with some new function calls. > > Currently I want to skip certain functions by adding the > no_instrument_function attribute. However, I do see that in

Define __attribute__((no_instrument_function)) but still got instrumented

2020-08-06 Thread Shuai Wang via Gcc
Hello! I am working on a ARM GCC plugin which instruments each GIMPLE function with some new function calls. Currently I want to skip certain functions by adding the no_instrument_function attribute. However, I do see that in the disassembled code, all functions are still instrumented. Am I miss

A problem with DECL_FIELD_OFFSET in something I declared

2020-08-06 Thread Gary Oblock via Gcc
This problem is from my structure reorganization optimization optimization code (simplified and cleaned to illustrate the problem. Here's what happening below at the high level >From the user program: typedef struct type type_t; struct type { double x; double y; }: I'll be creating: typede

gcc-8-20200806 is now available

2020-08-06 Thread GCC Administrator via Gcc
Snapshot gcc-8-20200806 is now available on https://gcc.gnu.org/pub/gcc/snapshots/8-20200806/ and on various mirrors, see http://gcc.gnu.org/mirrors.html for details. This snapshot has been generated from the GCC 8 git branch with the following options: git://gcc.gnu.org/git/gcc.git branch

Re: GCC 10.2: Spurious(?) stringop-overflow warning (not strlen/strcpy/etc.)

2020-08-06 Thread Martin Sebor via Gcc
On 8/6/20 2:14 PM, Martin Sebor wrote: On 8/3/20 10:58 PM, Paul Smith wrote: On Mon, 2020-08-03 at 17:02 -0600, Martin Sebor wrote: If the code is designed to treat Node sort of like a struct with a flexible array member I would suggest to make that explicit by adding a zero-element array membe

Re: GCC 10.2: Spurious(?) stringop-overflow warning (not strlen/strcpy/etc.)

2020-08-06 Thread Martin Sebor via Gcc
On 8/3/20 10:58 PM, Paul Smith wrote: On Mon, 2020-08-03 at 17:02 -0600, Martin Sebor wrote: If the code is designed to treat Node sort of like a struct with a flexible array member I would suggest to make that explicit by adding a zero-element array member to Node and using it to access other m

Re: gcc __attribute__

2020-08-06 Thread Marek Polacek via Gcc
On Thu, Aug 06, 2020 at 04:15:10PM +0100, Philip R Brenan via Gcc wrote: > Hi *GCC*: > > On page: > > https://gcc.gnu.org/onlinedocs/gcc-3.2/gcc/Function-Attributes.html > > you show the attribute coming after the parameter list. But when I try > this, I get the following: That manual is for

gcc __attribute__

2020-08-06 Thread Philip R Brenan via Gcc
Hi *GCC*: On page: https://gcc.gnu.org/onlinedocs/gcc-3.2/gcc/Function-Attributes.html you show the attribute coming after the parameter list. But when I try this, I get the following: #include void __attribute__ ((noreturn)) aaa() // OK {exit(0); } void bbb() __attribute__ ((noreturn))