improve syntax errors

2019-01-03 Thread Daniel Marjamäki
Hello! I have used GCC for decades and would like to contribute a little. :-) I would like to see if I can improve the syntax errors. Here is one example code: int x = 3) + 0; I have created this ugly experimental patch: --- a/gcc/c/c-parser.c +++ b/gcc/c/c-parser.c @@ -2228,7 +2228,10 @@

Re: improve syntax errors

2019-01-03 Thread David Malcolm
On Thu, 2019-01-03 at 15:59 +0100, Daniel Marjamäki wrote: > Hello! > > I have used GCC for decades and would like to contribute a little. :- > ) Hi, and welcome! > I would like to see if I can improve the syntax errors. > > Here is one example code: > > int x = 3) + 0; > > I have created

Re: improve syntax errors

2019-01-03 Thread Jonathan Wakely
On Thu, 3 Jan 2019 at 15:40, David Malcolm wrote: > > On Thu, 2019-01-03 at 15:59 +0100, Daniel Marjamäki wrote: > > Hello! > > > > I have used GCC for decades and would like to contribute a little. :- > > ) > > Hi, and welcome! > > > I would like to see if I can improve the syntax errors. > > > >

Re: syntax errors

2019-01-03 Thread Daniel Marjamäki
Thank you for the quick reply. > how about "stray %qs token"? I will change. > I wonder how much we want to special-case this. Are you thinking about > the case where there's a stray symbol in the code (perhaps due to a > stray keypress, or unfinished manual edits)? At the moment I only think a

Mais praticidade para suas compras online.

2019-01-03 Thread Santander
http://tr.santander.com.br/f/a/PPmjU4rVj0zTRnyGYvUq3A~~/AQA~/RgReEMorP0Q4aHR0cDovL3d3dy53My5vcmcvVFIveGh0bWwxL0RURC94aHRtbDEtdHJhbnNpdGlvbmFsLmR0ZCJXBXVuZWFyQgoAAitFLlxZy7umUgtnY2NAZ251Lm9yZ1gEAA~~> http://tr.santander.com.br/f/a/bMOvSvHWQ1mS1duk35pSMw~~/AQA~/RgReEMorP0QdaHR0cDovL3d3dy5

Re: syntax errors

2019-01-03 Thread Jonathan Wakely
On Thu, 3 Jan 2019 at 17:03, Daniel Marjamäki wrote: > > Thank you for the quick reply. > > > how about "stray %qs token"? > > I will change. > > > I wonder how much we want to special-case this. Are you thinking about > > the case where there's a stray symbol in the code (perhaps due to a > > str

Mtrace with no environment MALLOC_TRACE feature request mtrace_setpath.

2019-01-03 Thread Joseph Howard
Request for mtrace_setpath In debugging and profiling PAM (Pluggable Authentication Modules) modules for memory leaks in linux, mtrace cannot access environment variables as these do not exist until the authentication completes (e.g. /etc/environment . The MALLOC_TRACE path can only be supplie

Re: Mtrace with no environment MALLOC_TRACE feature request mtrace_setpath.

2019-01-03 Thread Jonathan Wakely
On Thu, 3 Jan 2019 at 21:18, Joseph Howard wrote: > > Request for mtrace_setpath I think you should have sent this to glibc, which is a completely separate project to GCC. See https://www.gnu.org/software/libc/libc.html

gcc-7-20190103 is now available

2019-01-03 Thread gccadmin
Snapshot gcc-7-20190103 is now available on ftp://gcc.gnu.org/pub/gcc/snapshots/7-20190103/ and on various mirrors, see http://gcc.gnu.org/mirrors.html for details. This snapshot has been generated from the GCC 7 SVN branch with the following options: svn://gcc.gnu.org/svn/gcc/branches/gcc-7

Re: improve syntax errors

2019-01-03 Thread Martin Sebor
On 1/3/19 8:40 AM, David Malcolm wrote: On Thu, 2019-01-03 at 15:59 +0100, Daniel Marjamäki wrote: Hello! I have used GCC for decades and would like to contribute a little. :- ) Hi, and welcome! I would like to see if I can improve the syntax errors. Here is one example code: int x =