Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
AMD Zen/Ryzen thread (part 2)
View unanswered posts
View posts from last 24 hours

Goto page Previous  1, 2, 3, 4, 5, 6, 7, 8  Next  
Reply to topic    Gentoo Forums Forum Index Gentoo Chat
View previous topic :: View next topic  
Author Message
Naib
Watchman
Watchman


Joined: 21 May 2004
Posts: 5689
Location: Removed by Neddy

PostPosted: Tue Sep 19, 2017 10:32 am    Post subject: Reply with quote

AlienPenguin wrote:
NeddySeagoon,
i do not have any ryzen system (was considering it for an upgrade though :P ) i was referring to the timings posted by other people in previous posts.

that is why i asked fro some clarifications :)


but...
AlienPenguin wrote:
Hi all,

these are my mesa compilation times...



I am really confused. You start by saying these are your times then say they are other peoples numbers from previous posts but those numbers do not appear in this thread oO

either way you must be careful reading too much into such numbers without additional information. As NeddySeagoon stated portage config can influence. Equally unless the usage is the same it cannot be compared (take my multiple parallel runs to stress my system).

That said... while a Ryzen CPU is a step change from previous generations of AMD chips, it isn't groundbreaking compared to recent intels with regards to performance
_________________
The best argument against democracy is a five-minute conversation with the average voter
Great Britain is a republic, with a hereditary president, while the United States is a monarchy with an elective king
Back to top
View user's profile Send private message
krinn
Watchman
Watchman


Joined: 02 May 2003
Posts: 7167

PostPosted: Tue Sep 19, 2017 10:34 am    Post subject: Reply with quote

emerge is not a benchmark, so many things can alter the timing.
With my i7-4790K i have
Code:
      Sat Apr 22 20:03:00 2017 >>> media-libs/mesa-17.0.4
       merge time: 3 minutes and 3 seconds.

     Thu Jul 27 16:13:21 2017 >>> media-libs/mesa-17.1.5
       merge time: 6 minutes and 3 seconds.

     Tue Sep 19 11:07:41 2017 >>> media-libs/mesa-17.2.0_rc5
       merge time: 8 minutes and 5 seconds.
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


Joined: 05 Jul 2003
Posts: 43754
Location: 56N 3W

PostPosted: Tue Sep 19, 2017 10:45 am    Post subject: Reply with quote

krinn,

Its perfectly clear that your i7-4790K is getting slower with age. :)
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.
Back to top
View user's profile Send private message
vaxbrat
l33t
l33t


Joined: 05 Oct 2005
Posts: 731
Location: DC Burbs

PostPosted: Tue Sep 19, 2017 12:50 pm    Post subject: gcc 5.4.0 experimental flags Reply with quote

Pasted the CFLAGS wiki for experimental use with 5.4.0 from here in my make.conf since it appears that djvu doesn't compile with 6.4.0.

https://wiki.gentoo.org/wiki/Ryzen#GCC

However my 5.4.0. barks about not recognizing -mclzero so I took that one out.
Back to top
View user's profile Send private message
vaxbrat
l33t
l33t


Joined: 05 Oct 2005
Posts: 731
Location: DC Burbs

PostPosted: Wed Sep 20, 2017 6:53 am    Post subject: theory for throttling back job limit when segfaults happen Reply with quote

I got through my emerge -e system and am about ready to reboot into my 4.13.1 kernel to run an emerge -e world. I only had a handful of packages that were segfaulting, so for those, I decided to throttle back my job limit from -j16 to -j4. My theory was that natural scheduler affinity would be to put the jobs into just the cores and not threads on the first die. That appeared to work since none of my packages that failed under 6.4.0 (other than ones that needed 5.4.0) would fail with -j4. For my very last package which was webkit-gtk that failed with a segfault, I throttled back to -j8 since I wanted to see if affinity would spread things out amongst only cores and not threads between the two dies. That also appears to work, but that is only one data point. So when I do my emerge -e world, I will throttle back to -j8 only for the entire run of 1600 or so to see whether I have any failures at that level.

I only had a handful of packages out of the slightly more than 1100 that would only compile under gcc 5.4.0. None of those had segfaulting problems.
Back to top
View user's profile Send private message
Tony0945
Advocate
Advocate


Joined: 25 Jul 2006
Posts: 3191
Location: Illinois, USA

PostPosted: Wed Sep 20, 2017 2:32 pm    Post subject: Reply with quote

vaxbrat, that would seem to validate AMD's earlier advice to disable SMT.
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


Joined: 05 Jul 2003
Posts: 43754
Location: 56N 3W

PostPosted: Wed Sep 20, 2017 2:52 pm    Post subject: Reply with quote

That's keeping a Ferrari just to drive to the corner shop.
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.
Back to top
View user's profile Send private message
Tony0945
Advocate
Advocate


Joined: 25 Jul 2006
Posts: 3191
Location: Illinois, USA

PostPosted: Wed Sep 20, 2017 3:13 pm    Post subject: Reply with quote

NeddySeagoon wrote:
That's keeping a Ferrari just to drive to the corner shop.
Good one!
Back to top
View user's profile Send private message
vaxbrat
l33t
l33t


Joined: 05 Oct 2005
Posts: 731
Location: DC Burbs

PostPosted: Thu Sep 21, 2017 12:42 am    Post subject: no segfaults after 1000 emerges Reply with quote

I'm about to break the 1000 build mark on my 1600 build emerge and have yet to have a segfault happen by throttling back to -j8. The only times I stopped are a few times when I had to switch back to gcc 5 for ebuilds that can't compile with 6.4.0. It probably also helped that the system toolchain probably had all of its non-zen bulldozer instructions flushed out by this point. When this is done, I may flip back to -j16 to see whether/how many sefaults I might still get.
Back to top
View user's profile Send private message
vaxbrat
l33t
l33t


Joined: 05 Oct 2005
Posts: 731
Location: DC Burbs

PostPosted: Thu Sep 21, 2017 2:20 pm    Post subject: Trying second emerge back at -j16 levels Reply with quote

That one finished okay and I found out my troubles with my amdgpu driver. It turns out the hdmi cable couldn't drive 4k res. When I swapped for a 4k displayport everything is happy happy.

I'm in the process of doing another 1600+ emerge -e world with -j16. If I hit a segfault, I'll try going back to -j12 with the theory that maybe trouble only breaks out when you have threads going across dies.
Back to top
View user's profile Send private message
mir3x
Guru
Guru


Joined: 02 Jun 2012
Posts: 431

PostPosted: Thu Sep 21, 2017 10:47 pm    Post subject: Reply with quote

I've sent mail to amd in monday, in tuesday i got rma from and resent it, in thursday i got resone that i can send. Im sending tomorrow to Netherlands.

I prepared my backup box.
I must say - one segfault per few days is nothing compared to that ubuntu on arm:
Code:


[   22.671017] tegradc 15210000.nvdisplay: hdmi: pclk:148500K, set prod-setting:prod_c_150M
[   44.907924] cinnamon[1793]: unhandled level 1 translation fault (11) at 0x00000000, esr 0x92000005
[   44.916955] pgd = ffffffc075bd5000
[   44.920462] [00000000] *pgd=0000000000000000, *pud=0000000000000000
[   44.928432] CPU: 0 PID: 1793 Comm: cinnamon Not tainted 4.4.38-tegra #1
[   44.935071] Hardware name: quill (DT)
[   44.938759] task: ffffffc1e03ea580 ti: ffffffc1cc4c0000 task.ti: ffffffc1cc4c0000
...
[   45.045760] Library at 0x7f9f61a87c: 0x7f9f5a3000 /lib/aarch64-linux-gnu/libc-2.23.so
[   45.053586] Library at 0x7f9fd02dd8: 0x7f9fcbd000 /usr/lib/aarch64-linux-gnu/libmuffin.so.0.0.0
[   45.062318] vdso base = 0x7f9fe58000
[   50.070350] cinnamon[1987]: unhandled level 1 translation fault (11) at 0x00000000, esr 0x92000005
[   50.079386] pgd = ffffffc1c1363000
[   50.082809] [00000000] *pgd=0000000000000000, *pud=0000000000000000

[   50.090662] CPU: 0 PID: 1987 Comm: cinnamon Not tainted 4.4.38-tegra #1
[   50.097299] Hardware name: quill (DT)
[   50.100980] task: ffffffc1c6254b00 ti: ffffffc1cc4c0000 task.ti: ffffffc1cc4c0000
[   50.108554] PC is at 0x7f962e687c
...
[   50.208490] Library at 0x7f962e687c: 0x7f9626f000 /lib/aarch64-linux-gnu/libc-2.23.so
[   50.216334] Library at 0x7f969cedd8: 0x7f96989000 /usr/lib/aarch64-linux-gnu/libmuffin.so.0.0.0
[   50.225097] vdso base = 0x7f96b24000
[   80.281300] cinnamon[2487]: unhandled level 1 translation fault (11) at 0x00000000, esr 0x92000005
[   80.290265] pgd = ffffffc06987e000
[   80.293701] [00000000] *pgd=0000000000000000, *pud=0000000000000000

[   80.301492] CPU: 5 PID: 2487 Comm: cinnamon Not tainted 4.4.38-tegra #1
[   80.308116] Hardware name: quill (DT)
...
[   80.418345] Library at 0x7f9681f87c: 0x7f967a8000 /lib/aarch64-linux-gnu/libc-2.23.so
[   80.426321] Library at 0x7f96f07dd8: 0x7f96ec2000 /usr/lib/aarch64-linux-gnu/libmuffin.so.0.0.0
[   80.435032] vdso base = 0x7f9705d000

...
[  153.479705] tegradc 15210000.nvdisplay: hdmi: pclk:148500K, set prod-setting:prod_c_150M
[  280.151413] lxqt-config-mon[3148]: unhandled level 2 translation fault (11) at 0x00000010, esr 0x92000006
[  280.161339] pgd = ffffffc1c13e6000
[  280.165392] [00000010] *pgd=000000022222c003, *pud=000000022222c003, *pmd=0000000000000000
...
[  280.293186] Library at 0x7f92e91d70: 0x7f92e7f000 /usr/lib/aarch64-linux-gnu/libKF5Screen.so.5.5.5
[  280.302151] Library at 0x7f92e91d70: 0x7f92e7f000 /usr/lib/aarch64-linux-gnu/libKF5Screen.so.5.5.5
[  280.311106] vdso base = 0x7f92f6c000
...
[  298.655208] tegradc 15210000.nvdisplay: hdmi: pclk:148500K, set prod-setting:prod_c_150M
[ 1213.707107] lxqt-config-mon[23441]: unhandled level 2 translation fault (11) at 0x00000010, esr 0x92000006
[ 1213.716814] pgd = ffffffc13cdd0000
[ 1213.720240] [00000010] *pgd=00000001e3105003, *pud=00000001e3105003, *pmd=000000000000000
...
[ 1213.847987] Library at 0x7f7f945d70: 0x7f7f933000 /usr/lib/aarch64-linux-gnu/libKF5Screen.so.5.5.5
[ 1213.856987] Library at 0x7f7f945d70: 0x7f7f933000 /usr/lib/aarch64-linux-gnu/libKF5Screen.so.5.5.5
[ 1213.866034] vdso base = 0x7f7fa21000
....
[ 1373.457049] tegradc 15210000.nvdisplay: hdmi: pclk:148500K, set prod-setting:prod_c_150M
[ 1490.166567] kactivitymanage[24154]: unhandled level 3 translation fault (11) at 0x7f6e51ccc0, esr 0x92000007
[ 1490.211042] pgd = ffffffc1cdfb5000
[ 1490.214501] [7f6e51ccc0] *pgd=00000002603e7003, *pud=00000002603e7003, *pmd=0000000254cb8003, *pte=0000000000000000
...
[ 1490.343960] Library at 0x7f740d753c: 0x7f740c2000 /usr/lib/aarch64-linux-gnu/libQt5Sql.so.5.5.1
[ 1490.352653] Library at 0x7f740d8bac: 0x7f740c2000 /usr/lib/aarch64-linux-gnu/libQt5Sql.so.5.5.1
[ 1490.361342] vdso base = 0x7f7abcf000
...
[ 1507.384774] tegradc 15210000.nvdisplay: hdmi: pclk:148500K, set prod-setting:prod_c_150M
[ 1763.169387] QXcbEventReader[25212]: unhandled level 3 translation fault (11) at 0x7f9125bf58, esr 0x83000007
[ 1763.179637] pgd = ffffffc1a8ef1000
[ 1763.183124] [7f9125bf58] *pgd=0000000228dda003, *pud=0000000228dda003, *pmd=0000000228ef8003, *pte=0000000000000000
...
[ 1763.313581] Library at 0x7f9125bf58: 0x7f91327000 /usr/lib/locale/locale-archive
[ 1763.321017] Library at 0x7f9125bf58: 0x7f91327000 /usr/lib/locale/locale-archive
[ 1763.328412] vdso base = 0x7f96b95000
[ 1787.759651] kactivitymanage[24865]: unhandled level 3 translation fault (11) at 0x7f903d3cc0, esr 0x92000007
[ 1787.782310] pgd = ffffffc1dd062000
[ 1787.785766] [7f903d3cc0] *pgd=000000024a777003, *pud=000000024a777003, *pmd=0000000216825003, *pte=0000000000000000

[ 1787.798220] CPU: 4 PID: 24865 Comm: kactivitymanage Not tainted 4.4.38-tegra #1
[ 1787.805574] Hardware name: quill (DT)
....
[ 1787.915591] Library at 0x7f9077c53c: 0x7f90767000 /usr/lib/aarch64-linux-gnu/libQt5Sql.so.5.5.1
[ 1787.924291] Library at 0x7f9077dbac: 0x7f90767000 /usr/lib/aarch64-linux-gnu/libQt5Sql.so.5.5.1
[ 1787.932980] vdso base = 0x7f97a74000

When replacement arrive I let u know.
_________________
Installation aborted to prevent system self-destruction
Back to top
View user's profile Send private message
Tony0945
Advocate
Advocate


Joined: 25 Jul 2006
Posts: 3191
Location: Illinois, USA

PostPosted: Thu Sep 21, 2017 11:37 pm    Post subject: Reply with quote

mir3x wrote:
I've sent mail to amd in monday, in tuesday i got rma from and resent it, in thursday i got resone that i can send. Im sending tomorrow to Netherlands.

Mir3x, this is not a criticism, just an aide to your English skills.

Quote:
I sent mail to AMD on Monday, on Tuesday, I got the RMA form and re-sent it, on Thursday, I got ???? that I can send. I'm sending it tomorrow to Netherlands.
Is it "the Netherlands"? That's what I was taught in school, but many countries are now resenting "the" in their names.

Don't know what you meant by "resone".

I feel like an old harpy schoolteacher, but I'd like someone to correct my German or Italian, so please take this in a friendly spirit.

Neddy and company will probably say I speak American, not English.
Back to top
View user's profile Send private message
vaxbrat
l33t
l33t


Joined: 05 Oct 2005
Posts: 731
Location: DC Burbs

PostPosted: Fri Sep 22, 2017 1:46 am    Post subject: no segfaults so far with -j16 Reply with quote

I got back from work and found things had stopped at the first ebuild that wouldn't compile under 6.4.0. That was after about 700. I don't know why things would be working all of a sudden when the only thing different is getting the display card and display working okay.
Back to top
View user's profile Send private message
vaxbrat
l33t
l33t


Joined: 05 Oct 2005
Posts: 731
Location: DC Burbs

PostPosted: Fri Sep 22, 2017 3:31 am    Post subject: serial number lookup Reply with quote

I just realized I had the cpu packaging sitting around and that has the serial number on it. Is there an AMD url to look that up and figure out week number? BTW things are still going just fine here without any segfaults.

TIA: My 1700x is PN YD17OXBCAEWOF sn 9GU8187O70072
Back to top
View user's profile Send private message
pjp
Administrator
Administrator


Joined: 16 Apr 2002
Posts: 18084

PostPosted: Fri Sep 22, 2017 5:55 am    Post subject: Reply with quote

Maybe this can help?
Code:
UA   1706       PGT
UA [YY][WW]  [1][2][3]

YY -> Year
WW -> Week
I think it was thought that anything after week 25 was supposed to be OK.
_________________
Those who know what's best for us must rise and save us from ourselves.
Back to top
View user's profile Send private message
mir3x
Guru
Guru


Joined: 02 Jun 2012
Posts: 431

PostPosted: Fri Sep 22, 2017 12:03 pm    Post subject: Reply with quote

Tony0945 wrote:

Mir3x, this is not a criticism, just an aide to your English skills.

Don't know what you meant by "resone".

Yeah, thx I guess :D. It was late and I was sleepy. Anyway everyone understood what I meant.
It was supposed to be "response" - "I got response that i can send".

I've sent today from Poland - DHL writes:
Quote:
Estimated Delivery:
Monday, September 25, 2017
By End of Day


I hope they send new cpu from EU not US or Canada.

Anyway I couldn't send from normal DHL shop, i had to go to their warehouse outside city. I was told there I need to go to international point, it wasn't far but at other side of highway which took a while. Guy in DHL wanted to see what's in box so I had to open it. Later I asked how much it would cost if I had to pay - guy said approx 60USD (wtf?, really).

pjp - that number like UA1706PGT is only on CPU. Maybe there is a way to find it via serial number but I couldn't google it.
vaxbrat gcc7.1 is kind of perfect, should be segfault free, u can try compiling gcc7.2 few times with any compiler, it will fail if ryzen is affected in about 15min-20mins (it uses temp compiler compiled in first minutes then, and it often fails)

Another edit :D : Im sitting on Jetson TX2, ubuntu, It seems compiling here is faster than on core 2 duo, but core 2duo was much snappier on gentoo. (but here youtube is flawless on fullhd, and it wasnt on core2duo with GF430GT)
_________________
Installation aborted to prevent system self-destruction
Back to top
View user's profile Send private message
Tony0945
Advocate
Advocate


Joined: 25 Jul 2006
Posts: 3191
Location: Illinois, USA

PostPosted: Fri Sep 22, 2017 12:16 pm    Post subject: Reply with quote

Detailed explanation here: https://www.reddit.com/r/Amd/comments/6scnlg/ryzen_reading_your_production_batch_number/
It's unclear whether all of these numbers are on the box. All are on the chip. I think you have to take off your heatsink and re-apply Arctic Silver or whatever.
Back to top
View user's profile Send private message
mouacyk
n00b
n00b


Joined: 23 Mar 2009
Posts: 13

PostPosted: Fri Sep 22, 2017 3:56 pm    Post subject: Reply with quote

mir3x wrote:

I must say - one segfault per few days is nothing compared to that ubuntu on arm:.

What about silent binary or data corruptions.
_________________
OCed24/7: 9900K5.0GHz//16GB4000MHzC16//1080Ti2.10GHz
OCed24/7: 1680v24.5GHz//32GB2333MHzC10//750Ti[GHz
Back to top
View user's profile Send private message
Naib
Watchman
Watchman


Joined: 21 May 2004
Posts: 5689
Location: Removed by Neddy

PostPosted: Fri Sep 22, 2017 5:28 pm    Post subject: Reply with quote

Well MSI have updated their bios for my mobo, agesa 1.0.0.6b & more RAM incompatibilities
the XMP profile finally has correct RAM timings so I didn't have to tweak the timing, only went for XMP-1 (2800) instead of the 3000 profile.

for the last 20min I have had 4 terminals open and each have had emerge mesa && emerge mesa && emerge mesa all four terminals have completed the 2nd emerge and the nct6775 sensor is indicating a temp (somewhere ...) of 53C

Code:

     Mon Sep 18 20:43:05 2017 >>> media-libs/mesa-17.2.1
       merge time: 5 minutes and 7 seconds.

     Fri Sep 22 17:59:46 2017 >>> media-libs/mesa-17.2.1
       merge time: 4 minutes and 43 seconds.

     Fri Sep 22 18:04:30 2017 >>> media-libs/mesa-17.2.1
       merge time: 9 minutes and 27 seconds.

     Fri Sep 22 18:09:11 2017 >>> media-libs/mesa-17.2.1
       merge time: 4 minutes and 34 seconds.

     Fri Sep 22 18:13:54 2017 >>> media-libs/mesa-17.2.1
       merge time: 4 minutes and 36 seconds.

     Fri Sep 22 18:18:35 2017 >>> media-libs/mesa-17.2.1
       merge time: 4 minutes and 34 seconds.

     Fri Sep 22 18:23:18 2017 >>> media-libs/mesa-17.2.1
       merge time: 4 minutes and 35 seconds.

     Fri Sep 22 18:28:11 2017 >>> media-libs/mesa-17.2.1
       merge time: 4 minutes and 45 seconds.


--edit --

all complete
Code:


     Fri Sep 22 17:59:46 2017 >>> media-libs/mesa-17.2.1
       merge time: 4 minutes and 43 seconds.

     Fri Sep 22 18:04:30 2017 >>> media-libs/mesa-17.2.1
       merge time: 9 minutes and 27 seconds.

     Fri Sep 22 18:09:11 2017 >>> media-libs/mesa-17.2.1
       merge time: 4 minutes and 34 seconds.

     Fri Sep 22 18:13:54 2017 >>> media-libs/mesa-17.2.1
       merge time: 4 minutes and 36 seconds.

     Fri Sep 22 18:18:35 2017 >>> media-libs/mesa-17.2.1
       merge time: 4 minutes and 34 seconds.

     Fri Sep 22 18:23:18 2017 >>> media-libs/mesa-17.2.1
       merge time: 4 minutes and 35 seconds.

     Fri Sep 22 18:28:11 2017 >>> media-libs/mesa-17.2.1
       merge time: 4 minutes and 45 seconds.

     Fri Sep 22 18:33:00 2017 >>> media-libs/mesa-17.2.1
       merge time: 4 minutes and 42 seconds.

     Fri Sep 22 18:37:50 2017 >>> media-libs/mesa-17.2.1
       merge time: 9 minutes and 32 seconds.

     Fri Sep 22 18:42:43 2017 >>> media-libs/mesa-17.2.1
       merge time: 4 minutes and 39 seconds.

     Fri Sep 22 18:47:26 2017 >>> media-libs/mesa-17.2.1
       merge time: 9 minutes and 22 seconds.

     Fri Sep 22 18:52:14 2017 >>> media-libs/mesa-17.2.1
       merge time: 14 minutes and 10 seconds.

_________________
The best argument against democracy is a five-minute conversation with the average voter
Great Britain is a republic, with a hereditary president, while the United States is a monarchy with an elective king
Back to top
View user's profile Send private message
Naib
Watchman
Watchman


Joined: 21 May 2004
Posts: 5689
Location: Removed by Neddy

PostPosted: Fri Sep 22, 2017 6:17 pm    Post subject: Reply with quote

Naib wrote:
wrc1944 wrote:
Naib,
I'd sure like to know your settings that allowed you to get that far. Congrats! :) (make.conf. settings, or any bios tweaks?)

I just ran an emerge -e @ system (458 packages) after a toolchain rebuild, finished perfectly (on 7.1.0-r1) in 2 hrs and 40 min. I figured I'd clean up @system first cause I did recently update glibc and wanted to eliminate that as any possible problem.

Then once again tried gcc-7.2.0 and still got the same problem at the usual 15-20 minutes into the compile:
Code:
    -o build/rtl.o /var/tmp/portage/sys-devel/gcc-7.2.0/work/gcc-7.2.0/gcc/rtl.c
/var/tmp/portage/sys-devel/gcc-7.2.0/work/gcc-7.2.0/gcc/genoutput.c: In function 'int main(int, const char**)':
/var/tmp/portage/sys-devel/gcc-7.2.0/work/gcc-7.2.0/gcc/genoutput.c:1039:1: internal compiler error: Segmentation fault
 }
 ^
0xb1810f crash_signal
        /var/tmp/portage/sys-devel/gcc-7.2.0/work/gcc-7.2.0/gcc/toplev.c:337
0xb59727 get_ref_base_and_extent(tree_node*, long*, long*, long*, bool*)
        /var/tmp/portage/sys-devel/gcc-7.2.0/work/gcc-7.2.0/gcc/tree-dfa.c:571
0xbdb800 ao_ref_base(ao_ref*)
        /var/tmp/portage/sys-devel/gcc-7.2.0/work/gcc-7.2.0/gcc/tree-ssa-alias.c:641
0x75b948 ao_ref_from_mem
        /var/tmp/portage/sys-devel/gcc-7.2.0/work/gcc-7.2.0/gcc/alias.c:298
0x75bcbc rtx_refs_may_alias_p
        /var/tmp/portage/sys-devel/gcc-7.2.0/work/gcc-7.2.0/gcc/alias.c:375
0x75bf8e write_dependence_p
        /var/tmp/portage/sys-devel/gcc-7.2.0/work/gcc-7.2.0/gcc/alias.c:3066
0x75c03f canon_anti_dependence(rtx_def const*, bool, rtx_def const*, machine_mode, rtx_def*)
        /var/tmp/portage/sys-devel/gcc-7.2.0/work/gcc-7.2.0/gcc/alias.c:3090
0x112f979 check_dependence
        /var/tmp/portage/sys-devel/gcc-7.2.0/work/gcc-7.2.0/gcc/cse.c:1815
0x112f979 invalidate
        /var/tmp/portage/sys-devel/gcc-7.2.0/work/gcc-7.2.0/gcc/cse.c:1945
0x1136801 cse_insn
        /var/tmp/portage/sys-devel/gcc-7.2.0/work/gcc-7.2.0/gcc/cse.c:5787
0x1138b6a cse_extended_basic_block
        /var/tmp/portage/sys-devel/gcc-7.2.0/work/gcc-7.2.0/gcc/cse.c:6569
0x1138b6a cse_main
        /var/tmp/portage/sys-devel/gcc-7.2.0/work/gcc-7.2.0/gcc/cse.c:6747
0x1139376 rest_of_handle_cse
        /var/tmp/portage/sys-devel/gcc-7.2.0/work/gcc-7.2.0/gcc/cse.c:7567
0x1139376 execute
        /var/tmp/portage/sys-devel/gcc-7.2.0/work/gcc-7.2.0/gcc/cse.c:7610
Please submit a full bug report,
with preprocessed source if appropriate.
Please include the complete backtrace with any bug report.
See <https://bugs.gentoo.org/> for instructions.
make[3]: *** [Makefile:2597: build/genoutput.o] Error 1
make[3]: *** Waiting for unfinished jobs....
rm gfortran.pod gcc.pod
make[3]: Leaving directory '/var/tmp/portage/sys-devel/gcc-7.2.0/work/build/gcc'
make[2]: *** [Makefile:4624: all-stage3-gcc] Error 2
make[2]: Leaving directory '/var/tmp/portage/sys-devel/gcc-7.2.0/work/build'
make[1]: *** [Makefile:22446: stage3-bubble] Error 2
make[1]: Leaving directory '/var/tmp/portage/sys-devel/gcc-7.2.0/work/build'
make: *** [Makefile:22521: bootstrap-lean] Error 2
 * ERROR: sys-devel/gcc-7.2.0::gentoo failed (compile phase):
 *   emake failed
It's obviously gcc-7.2 on Ryzen cpu and/or AM4 platforms, and/or linux//bios settings problems, as gcc-7.2.0 compiles and runs perfectly on my old AM3+ FX 8320 gigabyte system. It gives me new hope that you got 7.2 installed.



it might actually be a gcc-7.2 thing rather than ryzen. At least one confirmed regression in 7.2
https://gcc.gnu.org/ml/gcc-bugs/2017-09/msg00391.html

looking more and more likely that gcc-7.2 is buggy
https://stackoverflow.com/questions/46331365/why-does-g7-2-have-this-internal-compiler-error-when-compiling-this-home-made

also:
https://gcc.gnu.org/ml/gcc/2017-09/msg00103.html
Quote:
Invalid free in standard library in trivial example with C++17 on gcc 7.2



https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81338
_________________
The best argument against democracy is a five-minute conversation with the average voter
Great Britain is a republic, with a hereditary president, while the United States is a monarchy with an elective king


Last edited by Naib on Fri Sep 22, 2017 6:38 pm; edited 1 time in total
Back to top
View user's profile Send private message
Naib
Watchman
Watchman


Joined: 21 May 2004
Posts: 5689
Location: Removed by Neddy

PostPosted: Fri Sep 22, 2017 6:18 pm    Post subject: Reply with quote

mir3x wrote:

vaxbrat gcc7.1 is kind of perfect, should be segfault free, u can try compiling gcc7.2 few times with any compiler, it will fail if ryzen is affected in about 15min-20mins (it uses temp compiler compiled in first minutes then, and it often fails)

Gcc-7.2 could be buggy rather than aggravating Ryzen
_________________
The best argument against democracy is a five-minute conversation with the average voter
Great Britain is a republic, with a hereditary president, while the United States is a monarchy with an elective king
Back to top
View user's profile Send private message
thumper
Guru
Guru


Joined: 06 Dec 2002
Posts: 533
Location: Venice FL

PostPosted: Fri Sep 22, 2017 11:49 pm    Post subject: Reply with quote

Naib wrote:
Well MSI have updated their bios for my mobo, agesa 1.0.0.6b & more RAM incompatibilities
the XMP profile finally has correct RAM timings so I didn't have to tweak the timing, only went for XMP-1 (2800) instead of the 3000 profile.

for the last 20min I have had 4 terminals open and each have had emerge mesa && emerge mesa && emerge mesa all four terminals have completed the 2nd emerge and the nct6775 sensor is indicating a temp (somewhere ...) of 53C


I just loaded the bios update for my MSI X370 Carbon pro containing agesa 1.0.0.6b this morning and I could NEVER get through 2 passes compiling GCC 7.1.0 with this script (Active GCC is 7.2.0) and it's still going after 9 passes:
Code:

#  cat loop_gcc_build.sh
#!/bin/bash

while true; do
        if ! emerge -1v =sys-devel/gcc-7.1.0-r1; then break; fi;
done || exit 1


Don't know what the update did, but time will tell if it's a fix for me anyway.

I'm using all stock speeds and Auto voltages no XMP.

George
Back to top
View user's profile Send private message
vaxbrat
l33t
l33t


Joined: 05 Oct 2005
Posts: 731
Location: DC Burbs

PostPosted: Sat Sep 23, 2017 5:38 am    Post subject: getting some segfaults again with -j16 Reply with quote

Thought I had things under control but oh well. I fell back to -j12 and things seemed to behave after I got a segfault or two about 800 ebuilds in. We really should figure out if there's a way to tell build week number from the retail packaging serial number. I'm just beginning the process of retiring my fx-8350 and Kaveri boxes (when the apu version comes out), and I want to be able to go into MicroCenter and verify before I buy. I might end up building one threadripper just to have a seriously bad ass build and render server. It makes me cry thinking that work is still buying as new HP Z800 class workstations based on 6 generation old Sandy Bridge stuff and paying probably 3-4 times the price with the same amount of memory and a lot less disk.
Back to top
View user's profile Send private message
trippels
Tux's lil' helper
Tux's lil' helper


Joined: 24 Nov 2010
Posts: 137
Location: Berlin

PostPosted: Sun Sep 24, 2017 8:53 am    Post subject: Reply with quote

Naib wrote:
mir3x wrote:

vaxbrat gcc7.1 is kind of perfect, should be segfault free, u can try compiling gcc7.2 few times with any compiler, it will fail if ryzen is affected in about 15min-20mins (it uses temp compiler compiled in first minutes then, and it often fails)

Gcc-7.2 could be buggy rather than aggravating Ryzen


Would you please stop spouting this nonsense?
A gcc-7.2 bug would be 100% reproducible. Random gcc segfaults are always a hardware problem.
Back to top
View user's profile Send private message
Naib
Watchman
Watchman


Joined: 21 May 2004
Posts: 5689
Location: Removed by Neddy

PostPosted: Sun Sep 24, 2017 8:59 am    Post subject: Reply with quote

trippels wrote:
Naib wrote:
mir3x wrote:

vaxbrat gcc7.1 is kind of perfect, should be segfault free, u can try compiling gcc7.2 few times with any compiler, it will fail if ryzen is affected in about 15min-20mins (it uses temp compiler compiled in first minutes then, and it often fails)

Gcc-7.2 could be buggy rather than aggravating Ryzen


Would you please stop spouting this nonsense?
A gcc-7.2 bug would be 100% reproducible. Random gcc segfaults are always a hardware problem.


you mean like these (that I have already posted in this thead... this page non the less). The issue with 7.2 is 100% reproducible... it won't compile
https://gcc.gnu.org/ml/gcc-bugs/2017-09/msg00391.html
https://stackoverflow.com/questions/46331365/why-does-g7-2-have-this-internal-compiler-error-when-compiling-this-home-made
https://gcc.gnu.org/ml/gcc/2017-09/msg00103.html
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81338

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81661
_________________
The best argument against democracy is a five-minute conversation with the average voter
Great Britain is a republic, with a hereditary president, while the United States is a monarchy with an elective king


Last edited by Naib on Sun Sep 24, 2017 9:16 am; edited 1 time in total
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Gentoo Chat All times are GMT
Goto page Previous  1, 2, 3, 4, 5, 6, 7, 8  Next
Page 2 of 8

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum