From: Joel Brobecker <brobecker@adacore.com>
To: Stan Shebs <stan@codesourcery.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] Use vectors in uploaded tracepoints
Date: Wed, 07 Apr 2010 05:25:00 -0000 [thread overview]
Message-ID: <20100407052514.GG19194@adacore.com> (raw)
In-Reply-To: <4BBA62EC.7060601@codesourcery.com>
> The vector definition is probably harmless, although I'm generally
> reluctant to rely on the compiler + linker always doing the right
> thing with masses of static inline functions coming from headers.
> No doubt people will tell me I'm being paranoid, and the build would
> *never* fail with a complaint about duplicate symbols. :-)
I tend to be paranoid too, so that's at least two of us ;-). As I said,
whatever option you end up choosing will be fine. (in those cases,
when none of the options have clear benefits, I tend to stick to
the laziest one - maybe that's going to be most useful feedback of
the whole thread??? :-P)
--
Joel
prev parent reply other threads:[~2010-04-07 5:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-05 19:46 Stan Shebs
2010-04-05 20:51 ` Joel Brobecker
2010-04-05 22:24 ` Stan Shebs
2010-04-07 5:25 ` Joel Brobecker [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=20100407052514.GG19194@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=stan@codesourcery.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