public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "coryan+gccbugzilla at google dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/94087] std::random_device often fails when used from multiple threads
Date: Sun, 08 Mar 2020 12:09:08 +0000	[thread overview]
Message-ID: <bug-94087-4-MNy2UbVnX6@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-94087-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94087

--- Comment #5 from Carlos O'Ryan <coryan+gccbugzilla at google dot com> ---
(In reply to Andrew Pinski from comment #2)
> (In reply to Andrew Pinski from comment #1)
> > >The bug is *not* present on on Fedora:31 where the compiler reports:
> > 
> > I doubt it is version based but rather based on what the CPU you are running
> > on.
> 
> I Mean what type of CPU you are running on.


Oh, I missed that question, from /proc/cpuinfo (on Linux):

processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 94
model name : Intel(R) Core(TM) i7-6820HQ CPU @ 2.70GHz
stepping : 3
microcode : 0xd6
cpu MHz : 871.966
cache size : 8192 KB
physical id : 0
siblings : 8
core id : 0
cpu cores : 4
apicid : 0
initial apicid : 0
fpu : yes
fpu_exception : yes
cpuid level : 22
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36
clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm
constant_tsc art arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc
cpuid aperfmperf tsc_known_freq pni pclmulqdq dtes64 monitor ds_cpl vmx smx est
tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic movbe popcnt
tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch
cpuid_fault epb invpcid_single pti ssbd ibrs ibpb stibp tpr_shadow vnmi
flexpriority ept vpid fsgsbase tsc_adjust bmi1 hle avx2 smep bmi2 erms invpcid
rtm mpx rdseed adx smap clflushopt intel_pt xsaveopt xsavec xgetbv1 xsaves
dtherm ida arat pln pts hwp hwp_notify hwp_act_window hwp_epp md_clear
flush_l1d
bugs : cpu_meltdown spectre_v1 spectre_v2 spec_store_bypass l1tf mds swapgs taa
itlb_multihit
bogomips : 5424.00
clflush size : 64
cache_alignment : 64
address sizes : 39 bits physical, 48 bits virtual
power management:

  parent reply	other threads:[~2020-03-08 12:09 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-08  2:51 [Bug libstdc++/94087] New: " coryan+gccbugzilla at google dot com
2020-03-08  7:51 ` [Bug target/94087] " pinskia at gcc dot gnu.org
2020-03-08  7:51 ` pinskia at gcc dot gnu.org
2020-03-08  8:08 ` pinskia at gcc dot gnu.org
2020-03-08 12:04 ` coryan+gccbugzilla at google dot com
2020-03-08 12:09 ` coryan+gccbugzilla at google dot com [this message]
2020-03-09  9:44 ` redi at gcc dot gnu.org
2020-03-09 12:10 ` coryan+gccbugzilla at google dot com
2020-03-09 12:24 ` redi at gcc dot gnu.org
2020-04-23  3:30 ` wnereiz at kawashiro dot org
2020-05-14 10:27 ` rguenth at gcc dot gnu.org
2020-05-14 10:30 ` rguenth at gcc dot gnu.org
2020-05-14 10:44 ` redi at gcc dot gnu.org
2020-05-14 10:51 ` redi at gcc dot gnu.org
2020-05-14 11:35 ` redi at gcc dot gnu.org
2020-05-14 11:35 ` hjl.tools at gmail dot com
2020-05-14 11:37 ` rguenther at suse dot de
2020-05-14 11:38 ` rguenther at suse dot de
2020-05-14 11:41 ` rguenther at suse dot de
2020-05-14 11:46 ` redi at gcc dot gnu.org
2020-05-14 11:51 ` rguenther at suse dot de
2020-05-14 12:01 ` redi at gcc dot gnu.org
2020-05-14 12:02 ` redi at gcc dot gnu.org
2020-05-14 12:05 ` redi at gcc dot gnu.org
2020-05-19 22:23 ` cvs-commit at gcc dot gnu.org
2020-05-23  8:18 ` redi at gcc dot gnu.org
2020-07-09  8:49 ` avi@cloudius-systems.com
2020-07-09  9:14 ` cvs-commit at gcc dot gnu.org
2020-07-09  9:14 ` redi at gcc dot gnu.org

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-94087-4-MNy2UbVnX6@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).