question about illegal utf-8 encoding in string literals

2016-07-06 Thread Blower, Melanie
Hello
I work for Intel on the Intel C++ compiler and we strive to be compatible with 
the gnu compiler.
We are processing a source file assuming utf-8 encoding and we see a string 
literal with illegal utf-8 encoding, such as an 8-bit character with the high 
bit set like 0xa3.
Testing shows that gcc is passes the illegal utf-8 character through without 
diagnostic message, as though it were an "extended ascii" character.
I don't see a way to enable warnings for this issue.
Please confirm that gcc handles illegal utf-8 encodings this way.
Thanks and regards, Melanie Blower


RE: Transactional memory test case reduction failure

2018-08-27 Thread Blower, Melanie
There's probably something wrong with your "check.sh" causing it to not return 
0.  You need to debug the script. 

> -Original Message-
> From: sameeran joshi [mailto:gsocsamee...@gmail.com]
> Sent: Sunday, August 26, 2018 2:38 PM
> To: gcc@gcc.gnu.org
> Cc: Shubham Narlawar 
> Subject: Transactional memory test case reduction failure
> 
> Hi,
> I have found an ICE in the transaction memory extension while compiling a
> program with gcc,but unfortunately for filing a bug in the gcc bugzilla I am
> unable to reduce the buggy file with creduce .
> 
> I have included the command line option -fgnu-tm while compiling it.
> Does creduce support transactional memory for reduction?
> 
> In the interestingness test script,it
> always returns 1, also following message is displayed
> 
> C-Reduce cannot run because the interestingness test does not return zero.
> Please ensure that it does so not only in the directory where you are 
> invoking C-
> Reduce, but also in an arbitrary temporary directory containing only the files
> that are being reduced. In other words, running these commands:
> 
>   DIR=`mktemp -d`
>   cp /home/swamimauli/upload/csmith/runtime/del/testcase.c $DIR
>   cd $DIR
>   /home/swamimauli/upload/csmith/runtime/del/check.sh
>   echo $?
> 
> should result in "0" being echoed to the terminal.
> 
> See "creduce --help" for more information.
> 
> Thanks,
> Sameeran Joshi


RE: Transactional memory test case reduction failure

2018-08-27 Thread Blower, Melanie
The –Wall option probably doesn’t make a difference, warning can be issued and 
the return code is still 0.

I use creduce a lot.  Usually I have a “reference” compilation as well as the 
failure compilation.  In your case, possibly, the reference compilation would 
be to NOT use the –fsquiggle option (where squiggle enables the transactional 
memory).  You need to work on your script until it returns 0. At that point you 
can start up creduce.  Does your test have a main program? I think you probably 
want the “-c” option

I’m not that fluent with bash scripting—I think your “if” statement might be 
wrong. Here’s a script that works for me in a different case,

#!/bin/bash
#
#
timeout 30s g++  -w  -c test.c >/dev/null 2>&1 &&\
timeout 30s g++  -w –fsquiggle -c test.c 2>&1 | \
head -1 | grep "internal compiler error" >/dev/null 2>&1


notice the backslash turns it all into a single line. It requires g++ to 
compile successfully on the first line – I use timeout because sometimes the 
compiler goes into an infinite loop – the 2nd line requires the compiler to 
issue an internal error as the first line of output. Grep returns 0 if the 
pattern is found



From: sameeran joshi [mailto:gsocsamee...@gmail.com]
Sent: Monday, August 27, 2018 11:13 AM
To: Blower, Melanie 
Cc: gcc@gcc.gnu.org; Shubham Narlawar 
Subject: Re: Transactional memory test case reduction failure

Hi,thanks for helping.
Below is  the text file contain the shell script .
I tried removing the compiler flags like -Wall,still it's giving output as 1.
Please review.
Thanks,
Sameeran joshi

On 27-Aug-2018 7:41 PM, "Blower, Melanie" 
mailto:melanie.blo...@intel.com>> wrote:
There's probably something wrong with your "check.sh" causing it to not return 
0.  You need to debug the script.

> -Original Message-
> From: sameeran joshi 
> [mailto:gsocsamee...@gmail.com<mailto:gsocsamee...@gmail.com>]
> Sent: Sunday, August 26, 2018 2:38 PM
> To: gcc@gcc.gnu.org<mailto:gcc@gcc.gnu.org>
> Cc: Shubham Narlawar mailto:gsocshub...@gmail.com>>
> Subject: Transactional memory test case reduction failure
>
> Hi,
> I have found an ICE in the transaction memory extension while compiling a
> program with gcc,but unfortunately for filing a bug in the gcc bugzilla I am
> unable to reduce the buggy file with creduce .
>
> I have included the command line option -fgnu-tm while compiling it.
> Does creduce support transactional memory for reduction?
>
> In the interestingness test script,it
> always returns 1, also following message is displayed
>
> C-Reduce cannot run because the interestingness test does not return zero.
> Please ensure that it does so not only in the directory where you are 
> invoking C-
> Reduce, but also in an arbitrary temporary directory containing only the files
> that are being reduced. In other words, running these commands:
>
>   DIR=`mktemp -d`
>   cp /home/swamimauli/upload/csmith/runtime/del/testcase.c $DIR
>   cd $DIR
>   /home/swamimauli/upload/csmith/runtime/del/check.sh
>   echo $?
>
> should result in "0" being echoed to the terminal.
>
> See "creduce --help" for more information.
>
> Thanks,
> Sameeran Joshi



RE: Transactional memory test case reduction failure

2018-08-27 Thread Blower, Melanie
I’m going to let you take it from here.  I added notes in the bottom of 
previous message showing you how I would do it.

From: Shubham Narlawar [mailto:gsocshub...@gmail.com]
Sent: Monday, August 27, 2018 11:35 AM
To: Blower, Melanie 
Cc: sameeran joshi ; gcc@gcc.gnu.org
Subject: Re: Transactional memory test case reduction failure

Here is the file. I am getting some error in sending .sh file, so I send it as 
below.


#!/bin/bash

gcc -fgnu-tm testcase.c > out.txt 2>&1 &&\

if

grep 'internal compiler error' out.txt

then

   exit 0

else

   exit 1

fi

#! gcc -c -fgnu-tm testcase.c

On Mon, Aug 27, 2018 at 8:59 PM Blower, Melanie 
mailto:melanie.blo...@intel.com>> wrote:
The –Wall option probably doesn’t make a difference, warning can be issued and 
the return code is still 0.

I use creduce a lot.  Usually I have a “reference” compilation as well as the 
failure compilation.  In your case, possibly, the reference compilation would 
be to NOT use the –fsquiggle option (where squiggle enables the transactional 
memory).  You need to work on your script until it returns 0. At that point you 
can start up creduce.  Does your test have a main program? I think you probably 
want the “-c” option

I’m not that fluent with bash scripting—I think your “if” statement might be 
wrong. Here’s a script that works for me in a different case,

#!/bin/bash
#
#
timeout 30s g++  -w  -c test.c >/dev/null 2>&1 &&\
timeout 30s g++  -w –fsquiggle -c test.c 2>&1 | \
head -1 | grep "internal compiler error" >/dev/null 2>&1


notice the backslash turns it all into a single line. It requires g++ to 
compile successfully on the first line – I use timeout because sometimes the 
compiler goes into an infinite loop – the 2nd line requires the compiler to 
issue an internal error as the first line of output. Grep returns 0 if the 
pattern is found



From: sameeran joshi 
[mailto:gsocsamee...@gmail.com<mailto:gsocsamee...@gmail.com>]
Sent: Monday, August 27, 2018 11:13 AM
To: Blower, Melanie mailto:melanie.blo...@intel.com>>
Cc: gcc@gcc.gnu.org<mailto:gcc@gcc.gnu.org>; Shubham Narlawar 
mailto:gsocshub...@gmail.com>>
Subject: Re: Transactional memory test case reduction failure

Hi,thanks for helping.
Below is  the text file contain the shell script .
I tried removing the compiler flags like -Wall,still it's giving output as 1.
Please review.
Thanks,
Sameeran joshi

On 27-Aug-2018 7:41 PM, "Blower, Melanie" 
mailto:melanie.blo...@intel.com>> wrote:
There's probably something wrong with your "check.sh" causing it to not return 
0.  You need to debug the script.

> -Original Message-
> From: sameeran joshi 
> [mailto:gsocsamee...@gmail.com<mailto:gsocsamee...@gmail.com>]
> Sent: Sunday, August 26, 2018 2:38 PM
> To: gcc@gcc.gnu.org<mailto:gcc@gcc.gnu.org>
> Cc: Shubham Narlawar mailto:gsocshub...@gmail.com>>
> Subject: Transactional memory test case reduction failure
>
> Hi,
> I have found an ICE in the transaction memory extension while compiling a
> program with gcc,but unfortunately for filing a bug in the gcc bugzilla I am
> unable to reduce the buggy file with creduce .
>
> I have included the command line option -fgnu-tm while compiling it.
> Does creduce support transactional memory for reduction?
>
> In the interestingness test script,it
> always returns 1, also following message is displayed
>
> C-Reduce cannot run because the interestingness test does not return zero.
> Please ensure that it does so not only in the directory where you are 
> invoking C-
> Reduce, but also in an arbitrary temporary directory containing only the files
> that are being reduced. In other words, running these commands:
>
>   DIR=`mktemp -d`
>   cp /home/swamimauli/upload/csmith/runtime/del/testcase.c $DIR
>   cd $DIR
>   /home/swamimauli/upload/csmith/runtime/del/check.sh
>   echo $?
>
> should result in "0" being echoed to the terminal.
>
> See "creduce --help" for more information.
>
> Thanks,
> Sameeran Joshi



request for legal forms for copyright assignment

2009-04-10 Thread Blower, Melanie


TWIMC

I am an employee of Intel Corp. who will be making future contributions to gcc, 
binutils, gdb and glibc. I am writing to request copyright assignment forms, 
and other legal forms that are deemed necessary by FSF, which will enable me to 
contribute to gcc, binutils, gdb and glibc.

Thanks and best regards,

Melanie Blower
(p.s. I'm resending this because the first message was sent in html, sorry if 
you received a duplicate request)  BTW I have 2 colleagues in the same position 
of needing assignment forms from FSF.  Do you prefer to hear from them directly 
or may I pass along the forms to them after I receive from you?

Cf:


The FSF prefers that a contributor files a copyright assignment for large 
contributions. See some documentation by the FSF for details and contact us 
(either via the gcc@gcc.gnu.org list or the GCC maintainer that is taking care 
of your contributions) to obtain the relevant forms. The most common forms are 
an assignment for a specific change, an assignment for all future changes, and 
an employer disclaimer, if an employer or school owns work created by the 
developer. It's a good idea to send assignme...@gnu.org a copy of your request.
I