public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ian at airs dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug go/104832] gccgo / libgo Reproducibility Problem Date: Wed, 09 Mar 2022 06:10:31 +0000 [thread overview] Message-ID: <bug-104832-4-x2fllDxU1q@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-104832-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104832 --- Comment #4 from Ian Lance Taylor <ian at airs dot com> --- Can you show the differences in one or two of the files, as you did before? Thanks. ASLR could be a factor, but only in the sense that it would make it more likely to reveal a bug in the code. The code should produce identical output regardless of whether using ASLR or not.
next prev parent reply other threads:[~2022-03-09 6:10 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-03-08 1:54 [Bug go/104832] New: " toolybird at tuta dot io 2022-03-08 8:10 ` [Bug go/104832] " schwab@linux-m68k.org 2022-03-08 21:54 ` ian at airs dot com 2022-03-09 5:24 ` toolybird at tuta dot io 2022-03-09 6:10 ` ian at airs dot com [this message] 2022-03-09 6:36 ` toolybird at tuta dot io 2022-03-09 6:37 ` toolybird at tuta dot io 2022-03-27 2:27 ` toolybird at tuta dot io
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-104832-4-x2fllDxU1q@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: linkBe 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).