Re: Error with gcc 4.7.1

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: rbmj <rbmj@xxxxxxxxxxx>
Subject: Re: Error with gcc 4.7.1
From: Jonathan Wakely <jwakely.gcc@xxxxxxxxx>
Date: Thu, 1 Nov 2012 18:30:57 +0000
Cc: gcc-help <gcc-help@xxxxxxxxxxx>
Comment: DKIM? See http://www.dkim.org
Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys
In-reply-to: <CAH6eHdTqmP8+XUz6E6k3xVSYFU1B9s_o-fDiEo0xZEJ2q_0xaQ@mail.gmail.com>

On 1 November 2012 18:27, Jonathan Wakely wrote:
> On 1 November 2012 17:43, rbmj wrote:
>>  I'm assuming that PRIi64 is a #define to some literal string.
>
> Yes, as required by C99 and later standards.

Well, required if int64_t is provided anyway.

References:
- Error with gcc 4.7.1
  - From: Pranith Kumar
- Re: Error with gcc 4.7.1
  - From: rbmj
- Re: Error with gcc 4.7.1
  - From: Jonathan Wakely

Prev by Date: Re: Error with gcc 4.7.1
Next by Date: Re: Using GCC to verify code has no "functional change".
Previous by thread: Re: Error with gcc 4.7.1
Next by thread: Re: Error with gcc 4.7.1
Index(es):
- Date
- Thread

[Index of Archives] [Linux C Programming] [Linux Kernel] [eCos] [Fedora Development] [Fedora Announce] [Autoconf] [The DWARVES Debugging Tools] [Yosemite Campsites] [Yosemite News] [Linux GCC]

Powered by Linux