public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Joseph Myers <joseph@codesourcery.com>
To: <pawel.kunio@gmail.com>
Cc: <gcc@gcc.gnu.org>
Subject: Re: My 2nd attempt to devel for gcc
Date: Wed, 14 Apr 2021 17:24:19 +0000	[thread overview]
Message-ID: <alpine.DEB.2.22.394.2104141720320.94016@digraph.polyomino.org.uk> (raw)
In-Reply-To: <CALTpEH4fp5PmsLkW9tc3SdtCTKrryziSBzTuLxMwwhZvZLqFfQ@mail.gmail.com>

On Wed, 14 Apr 2021, pawel k. via Gcc wrote:

> My best guess is if we could hookify all target code everything callable
> either from frontends or midend, we could try to severly cut this estimate.

That's a 700-patch series (there are about 700 target macros).  For every 
target macro, it's necessary to work out the corresponding target hook 
interface, which shouldn't always correspond one-to-one to the macro 
interface (and hooks have well-defined argument types, which macros don't 
always), and deal with the conversion, covering all the irregular ways in 
which different targets define the macros (including e.g. cases where some 
architectures define a target macro differently for different target 
OSes).

-- 
Joseph S. Myers
joseph@codesourcery.com

  reply	other threads:[~2021-04-14 17:24 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-27 23:37 pawel k.
2021-03-28  0:26 ` Jonathan Wakely
2021-03-28  1:20   ` pawel k.
2021-03-28  9:34     ` Jonathan Wakely
2021-03-28  9:53       ` pawel k.
2021-03-28 11:54       ` pawel k.
2021-03-29 17:25 ` Joseph Myers
2021-04-14  5:43   ` pawel k.
2021-04-14 17:24     ` Joseph Myers [this message]
2021-04-14 17:31       ` Prathamesh Kulkarni

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=alpine.DEB.2.22.394.2104141720320.94016@digraph.polyomino.org.uk \
    --to=joseph@codesourcery.com \
    --cc=gcc@gcc.gnu.org \
    --cc=pawel.kunio@gmail.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).