https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118935
--- Comment #35 from Jerry DeLisle <jvdelisle at gcc dot gnu.org> --- (In reply to [email protected] from comment #34) > Hi, Jerry, > On Tue, Oct 27, 2026 at 08:18:50AM GMT, xry111 at gcc dot gnu.org wrote: > > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118935 > > > > --- Comment #33 from Xi Ruoyao <xry111 at gcc dot gnu.org> --- > > (In reply to Xi Ruoyao from comment #27) > > > (In reply to [email protected] from comment #25) > > > > The English version is archived read-only, see Chinese version v1.1 > > > > Page 48 > > > > about dbar hint. > > > > > > > > (In reply to [email protected] from comment #24) > > > > > Am 14.08.26 um 11:59 schrieb huangpei at loongson dot cn: > > > > > > Base on Comment 6 and Comment 15, we can confirm that there is data > > > > > > race > > > > > > between > > > > > > find_file0 and set_internal_unit/new_unit, but Comment 15 show that > > > > > > **Only** > > > > > > under very weakly-order memory model with Same address Read after > > > > > > Read Out of > > > > > > Oder, SEGV can be triggered. As far as I know, Only Loong64 meet > > > > > > this memory > > > > > > modal. So I do not think this bug can be triggered on POWER64 or > > > > > > ARM64； > > > > > > > > > > Out of curiosity: Where is this documented? I cannot find this in > > > > > > > > > > https://loongson.github.io/LoongArch-Documentation/LoongArch-Vol1- > > > > > EN#overview-of-memory-consistency > > > > > > > > > > . > > > > > > > > 3A6000+, while compatible with 3A50000, has changed this behavior by new > > > > CPUCFG. So this is not a problem on newer cpu > > > > > > But I can reproduce this failure on 3A6000. Something still does not add > > > up... > > > > My failure is triggered by --enable-default-ssp and it seems a different > > issue, > > independent to this one. > > Since Xi Ruoyao has comfirmed this bug is fixed, and I retest it and it > passed on r17-5555-ga88d82f24bd, can we close this PR? > > > > -- > > You are receiving this mail because: > > You are on the CC list for the bug. > > You are the assignee for the bug. Did someone push a change that fixed this?
