Andrew Haley wrote:
>
> It's possible, but probably not. Most bugs that appear at -O2 are
> coding errors, but let's wait before pushing to any judgment.
Thank to both of you (Andrew and Jack), I'll dig this deeper anyway.
Regard
--
Emmanuel Fleury | Room: 261
Associate Professor
On Thu, Apr 26, 2007 at 03:28:26PM +0200, Emmanuel Fleury wrote:
> But if the bug disappear when -O2 is turned off, I do suspect
> (*eventually*) some problem in the ARM back-end... Am I right ?
Probably/maybe/possibly. It also could be the case that MySQL is doing
something that invokes undefined
Emmanuel Fleury writes:
> Andrew Haley wrote:
> >
> > It seems that no-one has investigated what is really going on. All
> > the gdb backtraces are without any debuginfo, and no-one has looked at
> > where exactly the segfault happens. No-one has looked at the source
> > code that faults,
Andrew Haley wrote:
>
> It seems that no-one has investigated what is really going on. All
> the gdb backtraces are without any debuginfo, and no-one has looked at
> where exactly the segfault happens. No-one has looked at the source
> code that faults, or the assembly code generated by the comp
Emmanuel Fleury writes:
> Hi,
>
> I'm following a strange bug in MySQL Debian package for ARM plateforms:
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=411427
>
> It seems that compiling the exact same code without optimization option
> make it works.
>
> Could somebody take a quic
Hi,
I'm following a strange bug in MySQL Debian package for ARM plateforms:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=411427
It seems that compiling the exact same code without optimization option
make it works.
Could somebody take a quick look at the thread (link given before) and
tell m
