| === doko_ [n=doko@dslb-088-073-097-164.pools.arcor-ip.net] has joined #ubuntu-toolchain | ||
| === Keybuk [n=scott@quest.netsplit.com] has joined #ubuntu-toolchain | ||
| === mlpug [n=user@a84-231-238-186.elisa-laajakaista.fi] has joined #ubuntu-toolchain | ||
| === jbailey [n=jbailey@montreal.canonical.com] has joined #ubuntu-toolchain | ||
| jbailey | doko: around? | 07:41 |
|---|---|---|
| doko | jbailey: pong | 07:43 |
| jbailey | doko: The SIGILL, is it common? | 07:43 |
| jbailey | doko: I'm wondering if it's better to dig out the binaries, do an objdump -d and search for the bad instruction, and target those for rebuilds. | 07:44 |
| doko | jbailey: we do have two bug reports, one found in mysql, the other just reported to gcc | 07:44 |
| jbailey | So by implication, probably gnome, kernel, basic shell stuff, etc. is mostly working fine. | 07:45 |
| doko | jbailey: yeah, need to lear all instructions which are affected | 07:45 |
| doko | s /lear/learn/ | 07:45 |
| jbailey | I wonder how ugly it is for us to do that search? I remember we did something like that for looking for a symbol leak at one point. | 07:45 |
| doko | apparently he could install on this machine | 07:45 |
| doko | I have to find out about the instructions | 07:46 |
| doko | jbailey: for the __builtin_prefetch case it's enough to scan the sources | 08:04 |
| jbailey | Well, if we can look for a particular set of instructions it might be nice to do a scan once. | 08:06 |
| jbailey | Dunno how easy that is, though. | 08:07 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!