[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#333766: libc6: SIGBUS in libm on hppa breaks qt-x11-free

This one time, at band camp, Steve Langasek said:
> On Thu, Oct 13, 2005 at 07:26:43PM +0200, Aurelien Jarno wrote:
> > When looking at the assembly code generated with gcc-3.3/gcc-3.4 and 
> > with gcc-4.0, I see some differences:
> > I also don't speak hppa assembly, but it is obvious that the code does 
> > not use the same registers. Maybe the bug is in gcc which generates 
> > wrong code? At least the same source code built with gcc-3.3 and gcc-3.4 
> > is working correctly.
> No, it isn't:
> glibc (2.3.5-6.0.1) unstable; urgency=low
>   * On hppa, build using gcc-3.4.
>  -- Matthias Klose <doko@debian.org>  Sat, 17 Sep 2005 10:55:42 +0000
> This is the version of libc6 running on the buildd and in paer's unstable
> chroot where I reproduced the error.  So glibc is known to have problems on
> hppa when built with gcc-4.0, but this doesn't appear to be one of them.

I think you are misunderstanding him, Steve, or I am misunderstanding
the whole thing (which is not unlikely).  I think Aurelian is saying
that the same source code that you supplied builds and runs fine with
gcc-3.4, but not with gcc-4.0:

sgran@paer:~$ dchroot sid
Executing shell in chroot: /org/paer.debian.org/chroot/sid
sgran@paer:~$ cat test.c
#include <fenv.h>

int main() {
        int foo;
        fenv_t fenv;
sgran@paer:~$ gcc-3.4 -lm test.c -o test.3.4
sgran@paer:~$ gcc-4.0 -lm test.c -o test.4
sgran@paer:~$ ./test.3.4
sgran@paer:~$ ./test.4
Bus error

This certainly smells more like a compiler bug than anything.  The same
library and the same header files, 2 different compiler versions, 2

Take care,
|   ,''`.                                            Stephen Gran |
|  : :' :                                        sgran@debian.org |
|  `. `'                        Debian user, admin, and developer |
|    `-                                     http://www.debian.org |

Attachment: signature.asc
Description: Digital signature

Reply to: