Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Luis Machado <lgustavo@codesourcery.com>
To: Pedro Alves <palves@redhat.com>, <gdb-patches@sourceware.org>
Subject: Re: [PATCH] Prevent GCC from folding inline test functions
Date: Mon, 24 Aug 2015 16:11:00 -0000	[thread overview]
Message-ID: <55DB420B.70707@codesourcery.com> (raw)
In-Reply-To: <55DB412D.6040807@redhat.com>

On 08/24/2015 01:07 PM, Pedro Alves wrote:
> On 08/24/2015 04:59 PM, Luis Machado wrote:
>> On 08/24/2015 12:53 PM, Pedro Alves wrote:
>>> On 08/24/2015 04:48 PM, Luis Machado wrote:
>>>> --- a/gdb/testsuite/gdb.opt/inline-markers.c
>>>> +++ b/gdb/testsuite/gdb.opt/inline-markers.c
>>>> @@ -13,7 +13,7 @@
>>>>       You should have received a copy of the GNU General Public License
>>>>       along with this program.  If not, see <http://www.gnu.org/licenses/>.  */
>>>>
>>>> -extern int x, y;
>>>> +extern int x, y, z;
>>>
>>> z here should match the definition (should be volatile here too).
>>>
>>> Thanks,
>>> Pedro Alves
>>>
>>
>> Fixed with 91dddb86299bba404599551e9e2633b3c0e5c830.
>>
>
> Thanks.  Though,
>
>   -extern int x, y, z;
>   +extern int x, y;
>   +extern volatile z;
>
> I think this will cause trouble with newer gcc that default
> to gnu c11.  Since C99 that a missing type specifier is no
> longer implicitly assumed to be int.  Thus that should really be:
>
> extern volatile int z;
>
> Thanks,
> Pedro Alves
>

Fixed in 4422ac93e5d3d23dd441aadaa49c81356aa59b73.


      reply	other threads:[~2015-08-24 16:11 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-21 13:05 Luis Machado
2015-08-21 16:03 ` Pedro Alves
2015-08-24 15:49   ` Luis Machado
2015-08-24 15:54     ` Pedro Alves
2015-08-24 15:59       ` Luis Machado
2015-08-24 16:07         ` Pedro Alves
2015-08-24 16:11           ` Luis Machado [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=55DB420B.70707@codesourcery.com \
    --to=lgustavo@codesourcery.com \
    --cc=gdb-patches@sourceware.org \
    --cc=palves@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