Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: gdb-patches@sourceware.org, Phil Muldoon <pmuldoon@redhat.com>
Subject: Re: [PATCH] compile: Use libcc1.so->libcc1.so.0
Date: Thu, 23 Apr 2015 12:07:00 -0000	[thread overview]
Message-ID: <5538E05D.2060103@redhat.com> (raw)
In-Reply-To: <20150423115236.GB5959@host1.jankratochvil.net>

On 04/23/2015 12:52 PM, Jan Kratochvil wrote:
> On Thu, 23 Apr 2015 13:42:12 +0200, Pedro Alves wrote:
>>    desired base version and desired C-specific version.  If the
>>    request can be satisfied, a compatible gcc_context object will be
>>                                ^^^^^^^^^^
>>    returned.  Otherwise, the function returns NULL.  */
> 
> OK, that may mean that GCC is allowed to return compatible GCC_FE_VERSION_1
> API even when client asked for GCC_FE_VERSION_0.

Yes, if the versions are compatible, and if the version is recorded in
a field in the returned context structure, then will even be simpler to just
return the highest version compatible, than my suggestion of having gdb
try both v1 and fallback to v0, which can be left for when we decide to make
a vN+1 that is not compatible with vN.  This is just like duck typing.

> Thanks for the clarification although I do not find the comment so clear.

Thanks,
Pedro Alves


  reply	other threads:[~2015-04-23 12:07 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-21 21:36 Jan Kratochvil
2015-04-21 21:38 ` mail dup cancel: " Jan Kratochvil
2015-04-22 21:13 ` Phil Muldoon
2015-04-23  5:29   ` Jan Kratochvil
2015-04-23 10:53     ` Phil Muldoon
2015-04-23 11:24       ` Pedro Alves
2015-04-23 11:47       ` Jan Kratochvil
2015-04-23 11:59         ` Pedro Alves
2015-04-23 11:42 ` Pedro Alves
2015-04-23 11:51   ` Jan Kratochvil
2015-04-23 11:52   ` Jan Kratochvil
2015-04-23 12:07     ` Pedro Alves [this message]
2015-04-23 12:24       ` Jan Kratochvil

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=5538E05D.2060103@redhat.com \
    --to=palves@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=jan.kratochvil@redhat.com \
    --cc=pmuldoon@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