public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Simon Marchi <simon.marchi@polymtl.ca>
To: Tom Tromey <tom@tromey.com>
Cc: Simon Marchi via Gdb-patches <gdb-patches@sourceware.org>
Subject: Re: The defs.h / common-defs.h / server.h rule
Date: Fri, 23 Feb 2024 16:55:10 -0500	[thread overview]
Message-ID: <baee4c1c-6b79-4dd2-9d33-70e28085750b@polymtl.ca> (raw)
In-Reply-To: <87bk86yjob.fsf@tromey.com>



On 2024-02-23 16:06, Tom Tromey wrote:
> Simon> I suppose the other classic way to do this is with an -include flag,
> Simon> passed to the compiler?
> 
> I don't know if any projects do this, but traditionally it's not done by
> GNU-ish programs, I guess because -include was GCC-specific, i.e., not
> portable.

Do you think it would be acceptable today?  As far as I know, people
only build gdb with gcc and clang.  But I checked other compilers I
know:

 - icc has -include (it uses the clang frontend now, I think)
 - xlc has -qinclude (although it seems like there's a version with a
   clang frontend as well which supports -include too)

So, in this day and age, I'd be surprised if anyone compiled gdb with a
compiler that doesn't have some equivalent of -include.

Simon

  reply	other threads:[~2024-02-23 21:55 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <2f2f552a-0028-49cc-adbe-ca038c1e9acd@polymtl.ca>
2024-02-20 12:20 ` Andrew Burgess
2024-02-20 14:52 ` Tom Tromey
2024-02-20 15:14   ` Tom Tromey
2024-02-23 20:35   ` Simon Marchi
2024-02-23 21:06     ` Tom Tromey
2024-02-23 21:55       ` Simon Marchi [this message]
2024-02-27 14:54         ` Tom Tromey

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=baee4c1c-6b79-4dd2-9d33-70e28085750b@polymtl.ca \
    --to=simon.marchi@polymtl.ca \
    --cc=gdb-patches@sourceware.org \
    --cc=tom@tromey.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).