From: Keith Seitz <keiths@redhat.com>
To: gdb-patches@sourceware.org
Subject: Re: [PATCH] Add libcc1 v1 compatibility to C compile feature
Date: Fri, 27 Apr 2018 20:15:00 -0000 [thread overview]
Message-ID: <a388b3cd-4625-9ffa-3e5f-7049a90e11de@redhat.com> (raw)
In-Reply-To: <185032f6-78f1-fe2e-5b56-bf51143f4fed@redhat.com>
On 04/09/2018 05:39 AM, Pedro Alves wrote:
> On 02/22/2018 09:04 PM, Keith Seitz wrote:
>> From: Alexandre Oliva <aoliva@redhat.com>
>>
>> This patch adds v1 compatibiltiy to the C compile feature. The only change
>> in v1 concerns the handling of integer types, which permits GDB to specify the
>> built-in name for the type.
>>
>> As far as I know, the C frontend is still on v0, so this patch is purely
>> precautionary. [By default C++ compile uses the equivalent of the C
>> frontend's int_type and float_type (aka the "v1" versions).]
>>
>> gdb/ChangeLog:
>>
>> * compile/compile-c-types.c (convert_int, convert_float):
>> Update for C FE v1.
>
> OK.
I've pushed that. Thank you!
Keith
prev parent reply other threads:[~2018-04-27 20:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-22 21:05 Keith Seitz
2018-04-09 12:39 ` Pedro Alves
2018-04-27 20:15 ` Keith Seitz [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=a388b3cd-4625-9ffa-3e5f-7049a90e11de@redhat.com \
--to=keiths@redhat.com \
--cc=gdb-patches@sourceware.org \
/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).