| Summary: | sys-devel/gcc-5.4.0 random Internal Compiler Errors in various packages at various points | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | toraboracaveman |
| Component: | Current packages | Assignee: | Gentoo Toolchain Maintainers <toolchain> |
| Status: | RESOLVED OBSOLETE | ||
| Severity: | normal | ||
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | AMD64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: |
Build log 1
Build log 2 Build log 3 Build log 4 CPU Information Build environment |
||
|
Description
toraboracaveman
2017-06-17 23:21:29 UTC
Created attachment 476770 [details]
Build log 1
This is one of the oldest build logs representing one of my oldest attempts to emerge qtwebengine.
Created attachment 476772 [details]
Build log 2
Same as build log 1, except for being yet another attempt.
Created attachment 476774 [details]
Build log 3
Similar to the previous ones, except for me lowering the CPU frequency, but I *think* concurrent jobs (MAKEOPTS="-jX") was not 1. Not sure though.
Created attachment 476776 [details]
Build log 4
Same, except:
1. MAKEOPTS="-j1" -- I'm sure.
2. I also configured the intel_pstate driver (by cpupower) such that the maximum CPU power is around 1GHz. I also confirmed this via lscpu, and cpupower commands. Additionally.
3. I confirm that CPU temp. was about 58 Celsius degrees.
4. I confirm that dmesg and journalctl did not show any CPU throttling due to raised temperature.
In my view, this build log represents my sanest shot to get this done, but I failed nonetheless.
Created attachment 476778 [details]
CPU Information
This file is essentially my /proc/cpuinfo
Created attachment 476780 [details]
Build environment
This file contains the build environment when I emerge qtwebengine.
> Similar to the previous case, such internal compiler errors appear at random points.
> 3. By repeating again, I managed to get llvm and ncurses compiled. But I never managed to get qtwebengine. My theory is that qtwebengine is so large that the probability of having GCC crash randomly is about 1. But this is only a feeling, as I never managed to emerge qtwebengine.
gcc randomly segfaulting pretty much sounds like a memory issue on your side.
Do you still think it is a memory issue? Could you please be more specific about what kind of an issue? Exceeding memory capacity? Or faulty memory? As for exceeding, I see no oom-killer in dmesg or journalctl. As for faulty memory card, memtest86+ reports no memory errors for 2.5 passes. (In reply to Matthias Maier from comment #7) > > Similar to the previous case, such internal compiler errors appear at random points. > > 3. By repeating again, I managed to get llvm and ncurses compiled. But I never managed to get qtwebengine. My theory is that qtwebengine is so large that the probability of having GCC crash randomly is about 1. But this is only a feeling, as I never managed to emerge qtwebengine. > > > gcc randomly segfaulting pretty much sounds like a memory issue on your side. yes, it seems to this is a "dupe" of bug 20600 (just my two cents) Does it still happen on modern gcc? |