public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
To: Jakub Jelinek <jakub@redhat.com>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] libsanitizer: Check assembler support for symbol assignment [PR112563]
Date: Mon, 27 Nov 2023 14:20:25 +0100	[thread overview]
Message-ID: <yddv89nz61y.fsf@CeBiTec.Uni-Bielefeld.DE> (raw)
In-Reply-To: <ZWSUxMKnFradfdfJ@tucnak> (Jakub Jelinek's message of "Mon, 27 Nov 2023 14:08:20 +0100")

Hi Jakub,

>> 2023-11-23  Rainer Orth  <ro@CeBiTec.Uni-Bielefeld.DE>
>> 
>> 	libsanitizer:
>> 	PR libsanitizer/112563
>> 	* configure.ac (libsanitizer_cv_as_sym_assign): Check for
>> 	assembler symbol assignment support.
>> 	* configure, config.h.in: Regenerate.
>> 	* sanitizer_common/sanitizer_redefine_builtins.h: Include config.h.
>> 	Check HAVE_AS_SYM_ASSIGN.
>
> Can you please
> 1) split it into 2 patches, one touching config* which is owned by GCC (and
>    Makefiles, see later), one just sanitizer_common/sanitizer_redefine_builtins.h
> 2) avoid using config.h in, instead use AC_SUBST and add @HAVE_AS_SYM_ASSIGN@
>    to Makefile.am's DEFS where needed (either expanding to nothing or
>    -DHAVE_AS_SYM_ASSIGN=1)?  The reason is to minimize changes to imported
>    sources
>
> Once the sanitizer_common/sanitizer_redefine_builtins.h change (just
> the && defined(HAVE_AS_SYM_ASSIGN) addition) patch is committed and pushed
> upstream, add its commit has LOCAL_PATCHES.

But will they accept a patch to check a macro never set anywhere in and
irrelevant to LLVM?  That's why I kept all in one patch, to be GCC-local.

If we go (or at least try) this upstream route, should I wait for
approval there and than commit both parts to GCC, keeping it in my local
tree until then?

> Note, your ChangeLog entry was pretending config.h include has been added
> to one header, but it went to a different one instead.

Drats, that's what you get for starting one way and adjusting later ;-)

	Rainer

-- 
-----------------------------------------------------------------------------
Rainer Orth, Center for Biotechnology, Bielefeld University

  reply	other threads:[~2023-11-27 13:20 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-27 12:56 Rainer Orth
2023-11-27 13:08 ` Jakub Jelinek
2023-11-27 13:20   ` Rainer Orth [this message]
2023-11-27 13:26     ` Jakub Jelinek
2023-11-27 13:29       ` Rainer Orth
2023-11-28 13:16         ` Rainer Orth
2023-11-28 13:40           ` Jakub Jelinek

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=yddv89nz61y.fsf@CeBiTec.Uni-Bielefeld.DE \
    --to=ro@cebitec.uni-bielefeld.de \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jakub@redhat.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).