| Summary: | "sed" seg-faults on PPC with CFLAGS="...-fno-strict-aliasing..." | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | meyerm |
| Component: | [OLD] Core system | Assignee: | PPC Porters <ppc> |
| Status: | RESOLVED FIXED | ||
| Severity: | major | ||
| Priority: | High | ||
| Version: | 2004.3 | ||
| Hardware: | PPC | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
meyerm
2005-02-28 06:24:05 UTC
Oh, could someone please tell my why that flag is default in PPC make.conf? Does it make other problems? I will restart my update-world, this time without that flag and hopefully don't break anything other ;-) You don't need -funit-at-a-time, it's redundant with -O2. I also can't replicate the segfaults you're experiencing (I have my entire system compiled with -fno-strict-aliasing), but I feel like I've seen the problem before. The only real difference from my setup that you've got is that you're using -ftracer which shouldn't be a problem. I do have to ask if you're using kernel preemption. If you've got that enabled, please turn it off as it can cause random segfaults such as this. As for why we've got -fno-strict-aliasing on as default, we had a number of issues with miscompilation with gcc 3.3.3 without it. I'm not knowledgable about the current state of things to know if we still need that flag, but to my knowledge, it shouldn't hurt. If anyone else wants to chime in and clarify, feel free. > You don't need -funit-at-a-time, it's redundant with -O2. Whoops - thanks. Don't know why I used it. I got several CFLAGS (commented out) and my original/old ones don't have that flag. Perhaps I simply copied it out of someones make.conf without reading the manual again... > The only real difference from my setup that you've got is that > you're using -ftracer which shouldn't be a problem. Yes, since it works with that flag. And it is also not the combination, since it also segfaults when I use -no-strict-aliasing only. > I do have to ask if you're using kernel preemption. I haven't. Please note, that the segfault of sed was the only problem I encountered and I was deterministic/reproducable. Perhaps it helps (even though I don't believe it ;-) ) if I mention the following: The system was once set up with -fstack-protector. But since I got segfaults and problems with sooo many programs and nobody could help (hey, really no stack-protector-users on PPC?) I decided that using a PPC shall be enough protection for now ;-). But some libs and/or programs which weren't updated for a long time could still be "protected". OK, _it_ was deterministic... Ah... Simply ignore my english please. ;-p Aparently it was a stuffed up sed causing the problems, once replaced from a binary the issue was fixed. Niv, feel free to reopen the bug if it happens again. |
