Should -Wpedantic warn on use of __auto_type ?
For example, should it warn in the following case ?
int main()
{
__auto_type x = 3;
return 0;
}
I feel so, since __auto_type is non-standard. If it should warn, is
the following fix correct ? I ran the above code snippet (with the fix
applied)
Hi,
Here is the proposal to update x86-64 PLT for MPX. The linker change
is implemented on hjl/mpx/pltext8 branch. Any comments/feedbacks?
Thanks.
--
H.J.
---
Intel MPX:
http://software.intel.com/en-us/file/319433-017pdf
introduces 4 bound registers, which will be used for parameter passing
On 17/01/14 17:36, Eric Botcazou wrote:
I am not implying that this is a GCC bug, unless you think
WORD_REGISTER_OPERATIONS should have avoided the creation of such
paradoxical subreg.
No, that's precisely the contrary, WORD_REGISTER_OPERATIONS tends to create
paradoxical subregs.
I might th
> On Jan 18, 2014, at 12:04 PM, "Paulo J. Matos" wrote:
>
> On 17/01/14 17:36, Eric Botcazou wrote:
>>> I am not implying that this is a GCC bug, unless you think
>>> WORD_REISTER_OPERATIONS should have avoided the creation of such
>>> paradoxical subreg.
>>
>> No, that's precisely the contrar
Hello,
Do we care if trunk doesn't compile successfully with
--enable-werror-always?
Do we want to fix things like:
../../../../gcc-trunk/fixincludes/server.c: In function ‘server_setup’:
../../../../gcc-trunk/fixincludes/server.c:195:10: error: ignoring
return value of ‘getcwd’, declared wit
On 18/01/14 20:11, pins...@gmail.com wrote:
On Jan 18, 2014, at 12:04 PM, "Paulo J. Matos" wrote:
On 17/01/14 17:36, Eric Botcazou wrote:
I am not implying that this is a GCC bug, unless you think
WORD_REISTER_OPERATIONS should have avoided the creation of such
paradoxical subreg.
No, tha
On Sat, 18 Jan 2014, Prathamesh Kulkarni wrote:
> Should -Wpedantic warn on use of __auto_type ?
There is no general consistent rule followed for such reserved namespace
keywords. Your patch seems plausible (given testcase and %<%> quotes
around the keyword in the diagnostic text).
--
Joseph
On Sat, 18 Jan 2014, Paulo J. Matos wrote:
> Hello,
>
> Do we care if trunk doesn't compile successfully with --enable-werror-always?
The purpose of this option is to enable building of cross compilers to
fail on warnings in the same circumstances on which a native build would
fail (with the e
Snapshot gcc-4.7-20140118 is now available on
ftp://gcc.gnu.org/pub/gcc/snapshots/4.7-20140118/
and on various mirrors, see http://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 4.7 SVN branch
with the following options: svn://gcc.gnu.org/svn/gcc/branches
