>
> I don't know what gcc authors are smoking, but "strcpy(tmp,
> "what.");" will be compiled to a few mov instructions with -O0, while
> -Os still has a call to strcpy, just the way it *should* always be,
> imho.
not that it's any excuse, but -fno-builtin helps.
On Mon, Jun 15, 2015 at 4:56 PM,
On Mon, 15 Jun 2015 16:56:28 +0200
Siarhei Zirukin wrote:
> On Mon, Jun 15, 2015 at 3:41 PM, Ethan Grammatikidis
> wrote:
> > On Mon, 15 Jun 2015 09:21:56 +0100
> > Charles Forsyth wrote:
> >
> >> If you're using gcc 4.8.2 to compile ... anything, really ... but certainly
> >> Plan 9 or Inferno
On Mon, Jun 15, 2015 at 3:41 PM, Ethan Grammatikidis
wrote:
> On Mon, 15 Jun 2015 09:21:56 +0100
> Charles Forsyth wrote:
>
>> If you're using gcc 4.8.2 to compile ... anything, really ... but certainly
>> Plan 9 or Inferno components,
>> and those use for loops with arrays, be sure to include th
Ugh, I know. It caused Judy arrays to segfault a lot.
>From my personal experience, Clang does *not* have this problem.
On June 15, 2015 3:21:56 AM CDT, Charles Forsyth
wrote:
>If you're using gcc 4.8.2 to compile ... anything, really ... but
>certainly
>Plan 9 or Inferno components,
>and thos
On Mon, 15 Jun 2015 09:21:56 +0100
Charles Forsyth wrote:
> If you're using gcc 4.8.2 to compile ... anything, really ... but certainly
> Plan 9 or Inferno components,
> and those use for loops with arrays, be sure to include the compilation
> options
> -fno-strict-aliasing\
> -fno-aggressive-loo
If you're using gcc 4.8.2 to compile ... anything, really ... but certainly
Plan 9 or Inferno components,
and those use for loops with arrays, be sure to include the compilation
options
-fno-strict-aliasing\
-fno-aggressive-loop-optimizations\
and it will save you some time and effort.
It will save
