> I guess it probably doesn't apply in this case (if you've straced the
> simulator), but please also keep in mind another gotcha:
>
> http://gcc.gnu.org/ml/gcc/2006-12/msg00561.html
Yeah, doesn't apply. There were no *attempts* at I/O from the
simulator. I'm more inclined to think that th
Hi DJ
> Is sh-elf/sim supposed to support profiling? My latest tests show all
> the profiling tests failing. For example, the bprob executable has
> the name of the gcda file in it, but doesn't attempt to write it out
> (verified with strace against the simulator).
I guess it probably doesn't a
> Hmm... Did you try --with-headers?
I'll give that a try.
DJ Delorie <[EMAIL PROTECTED]> wrote:
>> Is your gcc configured with --with-newlib --with-headers?
>
> $TOP/gcc/gcc/configure --prefix=$PREFIX --target=$TARGET \
> --enable-languages=c,c++ --with-newlib --with-mpfr=/usr/local
>
> I do a two-phase build. I build gcc (and let it fail for libgcc)
> Is your gcc configured with --with-newlib --with-headers?
$TOP/gcc/gcc/configure --prefix=$PREFIX --target=$TARGET \
--enable-languages=c,c++ --with-newlib --with-mpfr=/usr/local
I do a two-phase build. I build gcc (and let it fail for libgcc) to
get xgcc/cc1, then build and install newlib,
DJ Delorie <[EMAIL PROTECTED]> wrote:
> Is sh-elf/sim supposed to support profiling? My latest tests show all
> the profiling tests failing. For example, the bprob executable has
> the name of the gcda file in it, but doesn't attempt to write it out
> (verified with strace against the simulator).
Is sh-elf/sim supposed to support profiling? My latest tests show all
the profiling tests failing. For example, the bprob executable has
the name of the gcda file in it, but doesn't attempt to write it out
(verified with strace against the simulator).
