From: Alexandre Oliva <oliva@adacore.com>
To: gcc-patches@gcc.gnu.org
Cc: Tom Tromey <tromey@adacore.com>, Jason Merrill <jason@redhat.com>,
Cary Coutant <ccoutant@gmail.com>,
Jakub Jelinek <jakub@redhat.com>,
David Edelsohn <dje.gcc@gmail.com>,
Segher Boessenkool <segher@kernel.crashing.org>,
Kewen Lin <linkw@gcc.gnu.org>
Subject: Re: [PATCH v2 #1/2] enable adjustment of return_pc debug attrs
Date: Thu, 27 Apr 2023 06:40:21 -0300 [thread overview]
Message-ID: <orfs8lwtmi.fsf@lxoliva.fsfla.org> (raw)
In-Reply-To: <orbkjq7dsq.fsf@lxoliva.fsfla.org> (Alexandre Oliva's message of "Fri, 14 Apr 2023 11:12:53 -0300")
On Apr 14, 2023, Alexandre Oliva <oliva@adacore.com> wrote:
> On Mar 23, 2023, Alexandre Oliva <oliva@adacore.com> wrote:
>> This patch introduces infrastructure for targets to add an offset to
>> the label issued after the call_insn to set the call_return_pc
>> attribute. This will be used on rs6000, that sometimes issues another
>> instruction after the call proper as part of a call insn.
> Ping?
> https://gcc.gnu.org/pipermail/gcc-patches/2023-March/614452.html
> https://gcc.gnu.org/pipermail/gcc-patches/2023-March/614453.html
Ping?
--
Alexandre Oliva, happy hacker https://FSFLA.org/blogs/lxo/
Free Software Activist GNU Toolchain Engineer
Disinformation flourishes because many people care deeply about injustice
but very few check the facts. Ask me about <https://stallmansupport.org>
prev parent reply other threads:[~2023-04-27 9:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-23 3:12 Alexandre Oliva, Alexandre Oliva
2023-03-23 3:15 ` [PATCH v2 #2/2] [rs6000] adjust " Alexandre Oliva
2023-04-14 14:12 ` [PATCH v2 #1/2] enable adjustment of " Alexandre Oliva
2023-04-27 9:40 ` Alexandre Oliva [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=orfs8lwtmi.fsf@lxoliva.fsfla.org \
--to=oliva@adacore.com \
--cc=ccoutant@gmail.com \
--cc=dje.gcc@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=jason@redhat.com \
--cc=linkw@gcc.gnu.org \
--cc=segher@kernel.crashing.org \
--cc=tromey@adacore.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).