public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "vmakarov at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/102147] IRA dependent on 32-bit vs 64-bit pointer size
Date: Wed, 01 Sep 2021 14:21:10 +0000 [thread overview]
Message-ID: <bug-102147-4-517tji4fUK@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-102147-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102147
--- Comment #6 from Vladimir Makarov <vmakarov at gcc dot gnu.org> ---
(In reply to David Edelsohn from comment #5)
> Vlad privately commented: "I suspect order of processing conflicts might
> depend on their representation."
>
> The two representations may produce different results and the heuristics to
> choose the representation depend on the pointer size.
Yes.
I'll be working on the PR. It is an interesting type of problem. I think GCC
output should be the same independently what type of compiler (64-bit or 32-bit
one) we use for building GCC.
next prev parent reply other threads:[~2021-09-01 14:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-31 15:13 [Bug rtl-optimization/102147] New: IRA dependent on 32-bit vs 64-bit register size dje at gcc dot gnu.org
2021-08-31 15:16 ` [Bug rtl-optimization/102147] " dje at gcc dot gnu.org
2021-08-31 15:24 ` dje at gcc dot gnu.org
2021-09-01 8:34 ` [Bug rtl-optimization/102147] IRA dependent on 32-bit vs 64-bit pointer size rguenth at gcc dot gnu.org
2021-09-01 8:36 ` rguenth at gcc dot gnu.org
2021-09-01 13:52 ` dje at gcc dot gnu.org
2021-09-01 14:21 ` vmakarov at gcc dot gnu.org [this message]
2021-09-22 18:11 ` vmakarov at gcc dot gnu.org
2021-09-24 15:15 ` cvs-commit at gcc dot gnu.org
2023-10-12 4:17 ` bergner 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-102147-4-517tji4fUK@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).