On Tue, Nov 15, 2016 at 1:19 PM, Eric Botcazou wrote:
>> Yes, I know -fno-strict-aliasing is globally set, but will all
>> -fstrict-aliasing optimization attributes on functions be "overwritten"?
>> That is, are you sure that when optimizing a function originally compiled
>> with -fstrict-aliasing
> Yes, I know -fno-strict-aliasing is globally set, but will all
> -fstrict-aliasing optimization attributes on functions be "overwritten"?
> That is, are you sure that when optimizing a function originally compiled
> with -fstrict-aliasing that -fno-strict-aliasing is in effect?
Do you mean with
On Tue, Nov 15, 2016 at 10:47 AM, Eric Botcazou wrote:
>> Can you verify that a TU compiled with -fstrict-aliasing will link as
>> if -fno-strict-aliasing if -fno-strict-aliasing is specified at link time?
>
> Yes, it does:
>
> eric@polaris:~/build/gcc/native> ~/install/gcc/bin/gcc -c t.c -O2 -flt
> Can you verify that a TU compiled with -fstrict-aliasing will link as
> if -fno-strict-aliasing if -fno-strict-aliasing is specified at link time?
Yes, it does:
eric@polaris:~/build/gcc/native> ~/install/gcc/bin/gcc -c t.c -O2 -flto
eric@polaris:~/build/gcc/native> ~/install/gcc/bin/gcc -o t t.
On Sun, Nov 13, 2016 at 11:31 PM, Eric Botcazou wrote:
> It's the note issued by the -Wlto-type-mismatch warning:
>
> q.ads:7:13: warning: type of 'q__proc' does not match original declaration [-
> Wlto-type-mismatch]
>procedure Proc (A : Arr);
> ^
> q.adb:7:3: note: 'q__proc' was
It's the note issued by the -Wlto-type-mismatch warning:
q.ads:7:13: warning: type of 'q__proc' does not match original declaration [-
Wlto-type-mismatch]
procedure Proc (A : Arr);
^
q.adb:7:3: note: 'q__proc' was previously declared here
procedure Proc (A : Arr) is begin null;
