From: kenner@adacore.com (Richard Kenner)
To: jeffreyalaw@gmail.com
Cc: gcc-patches@gcc.gnu.org, gnu-toolchain@rivosinc.com,
jakub@redhat.com, jivanhakobyan9@gmail.com, kito.cheng@gmail.com,
palmer@rivosinc.com, rdapp.gcc@gmail.com,
roger@nextmovesoftware.com, vineetg@rivosinc.com
Subject: Re: [RFC] expr: don't clear SUBREG_PROMOTED_VAR_P flag for a promoted subreg [target/111466]
Date: Thu, 05 Oct 2023 10:56:05 EDT [thread overview]
Message-ID: <20231005145605.18E8533CEF@vlsi2.gnat.com> (raw)
In-Reply-To: <2aab5d77-b9a5-490b-99db-693f88481809@gmail.com>
> At that particular time I think Kenner was mostly focused on the alpha
> and ppc ports, but I think he was also still poking around with romp and
> a29k. I think romp is an unlikely target for this because it didn't
> promote modes and it wasn't even building for several months
> (April->late July).
Obviously, I have no recollection of that change at all.
In July of 1994, I don't believe I was actively working on much in the
way of ports, though I could be misremembering. My guess is that this
change was to fix some bug, but I'm a bit mystified why I'd have
batched so many different changes together in one ChangeLog entry like
that. I think you're correct that it was most likely the Alpha that
showed the bug.
next prev parent reply other threads:[~2023-10-05 14:56 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-28 21:43 Vineet Gupta
2023-09-29 3:17 ` Jeff Law
2023-09-29 3:49 ` Vineet Gupta
2023-09-29 12:14 ` Jeff Law
2023-10-03 1:29 ` Vineet Gupta
2023-10-05 14:56 ` Richard Kenner [this message]
2023-10-05 15:04 ` Jeff Law
2023-09-29 10:40 ` Roger Sayle
2023-09-29 13:43 ` Jeff Law
2023-10-04 15:29 ` Jeff Law
2023-10-04 17:59 ` Jeff Law
2023-10-04 18:14 ` Vineet Gupta
2023-10-04 20:11 ` Jeff Law
2023-10-05 4:49 ` Jeff Law
2023-10-05 13:33 ` Robin Dapp
2023-10-05 16:42 ` Jeff Law
2023-10-12 2:37 ` Hans-Peter Nilsson
2023-10-12 16:11 ` Vineet Gupta
2023-10-17 4:07 ` Jeff Law
2023-10-17 18:06 ` Vineet Gupta
2023-10-17 18:07 ` [PATCH] RISC-V/testsuite/pr111466.c: fix expected output to not detect SEXT.W Vineet Gupta
2023-10-17 18:51 ` [PATCH v2] RISC-V/testsuite/pr111466.c: update test and expected output Vineet Gupta
2023-10-17 19:45 ` Jeff Law
2023-10-17 20:14 ` [COMMITTED] " Vineet Gupta
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=20231005145605.18E8533CEF@vlsi2.gnat.com \
--to=kenner@adacore.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gnu-toolchain@rivosinc.com \
--cc=jakub@redhat.com \
--cc=jeffreyalaw@gmail.com \
--cc=jivanhakobyan9@gmail.com \
--cc=kito.cheng@gmail.com \
--cc=palmer@rivosinc.com \
--cc=rdapp.gcc@gmail.com \
--cc=roger@nextmovesoftware.com \
--cc=vineetg@rivosinc.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).