public inbox for gnu-gabi@sourceware.org
 help / color / mirror / Atom feed
From: Florian Weimer <fweimer@redhat.com>
To: Jozef Lawrynowicz <jozef.l@mittosystems.com>
Cc: gnu-gabi@sourceware.org
Subject: Re: [RFC] Proposal for new ELF extension - "Symbol meta-information"
Date: Mon, 31 Aug 2020 14:23:57 +0200	[thread overview]
Message-ID: <875z8zj95u.fsf@oldenburg2.str.redhat.com> (raw)
In-Reply-To: <20200831115859.mwcruabbzoj3x4w7@jozef-acer-manjaro> (Jozef Lawrynowicz's message of "Mon, 31 Aug 2020 12:58:59 +0100")

* Jozef Lawrynowicz:

> I wonder if it is appropriate for inclusion in the GNU gABI or if we
> should just add it to a processor-specific ABI. However, it is being
> used downstream for MSP430 and ARM targets, in GCC and Clang/LLVM
> respectively. So we'd like to have it standardized somewhere generic
> so that different targets and toolchains can align on it.

Is there an expectation to upstream these changes?  In the present state
there does not seem to be need for such coordination.

>     3.3.3 SMT_PRINTF_FMT use case

Can this achieved in C++ with a library-only solution?  So that

  printf ("%s", str);

and

  printf ("%f", num);

resolve to different printf symbols externally?

Thanks,
Florian


  reply	other threads:[~2020-08-31 12:24 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-31 11:58 Jozef Lawrynowicz
2020-08-31 12:23 ` Florian Weimer [this message]
2020-08-31 13:14   ` Jozef Lawrynowicz
2020-08-31 13:45   ` James Y Knight
2020-09-01 11:20     ` Florian Weimer
2020-09-01 12:19       ` Jozef Lawrynowicz
2020-09-01 12:48         ` Florian Weimer
2020-09-02 10:26           ` Jozef Lawrynowicz
2020-09-03 16:49             ` Jozef Lawrynowicz

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=875z8zj95u.fsf@oldenburg2.str.redhat.com \
    --to=fweimer@redhat.com \
    --cc=gnu-gabi@sourceware.org \
    --cc=jozef.l@mittosystems.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).