From: Gabriel Ravier <gabravier@gmail.com>
To: Vru Inbvi <vru.inbvi@gmail.com>, gcc-help@gcc.gnu.org
Subject: Re: [wwwdocs] GCC processor independent install?
Date: Mon, 26 Feb 2024 22:06:26 +0000 [thread overview]
Message-ID: <06bbf36d-8c3d-4f60-887e-f8f1590ec397@gmail.com> (raw)
In-Reply-To: <CANwm-X022J66A1+tKvaaGD0yC0R3dZcG4OEjga250QsbLooSDA@mail.gmail.com>
On 2/26/24 21:59, Vru Inbvi via Gcc-help wrote:
> Hi,
>
> If I install for instance Ubuntu 22.04 with the default compilers (from apt
> install) on computers with AMD and Intel processors, and run my application
> I get the same results, bit for bit.
>
> However if I install a different version of GCC and GFORTRAN from source I
> get different results.
>
> Which configuration options should I use make my install
> processor-independent and get the same results?
>
> VI
I don't exactly understand what it is you're trying to say here,
exactly... If you're installing different versions of GCC (e.g. GCC 12
and GCC 13) then I would hope it is obvious enough that the different
versions will pretty much always output different code - even for minor
version updates this can often occur. If the issue is that your
application appears to exhibit different behavior (and not just have
differing executable artifacts) depending on the version this is most
likely due to a bug in your program, which you might be able to find
using checkers like `-fsanitize` or others, or, much less likely, there
is a bug in one of the two versions of GCC you used to compile the code.
prev parent reply other threads:[~2024-02-26 22:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-26 21:59 Vru Inbvi
2024-02-26 22:06 ` Gabriel Ravier [this message]
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=06bbf36d-8c3d-4f60-887e-f8f1590ec397@gmail.com \
--to=gabravier@gmail.com \
--cc=gcc-help@gcc.gnu.org \
--cc=vru.inbvi@gmail.com \
/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).