Re: anti-ranges of signed variables

2016-11-13 Thread Jakub Jelinek
On Mon, Nov 14, 2016 at 02:13:51PM +1100, kugan wrote: > I think we should change the get_range_info to: > > diff --git a/gcc/tree-ssanames.c b/gcc/tree-ssanames.c > index 913d142..f33b9c0 100644 > --- a/gcc/tree-ssanames.c > +++ b/gcc/tree-ssanames.c > @@ -371,7 +371,7 @@ get_range_info (const_tr

Re: anti-ranges of signed variables

2016-11-13 Thread kugan
I think we should change the get_range_info to: diff --git a/gcc/tree-ssanames.c b/gcc/tree-ssanames.c index 913d142..f33b9c0 100644 --- a/gcc/tree-ssanames.c +++ b/gcc/tree-ssanames.c @@ -371,7 +371,7 @@ get_range_info (const_tree name, wide_int *min, wide_int *max) *min = ri->get_min ()

Re: anti-ranges of signed variables

2016-11-13 Thread kugan
Hi, On 12/11/16 06:19, Jakub Jelinek wrote: On Fri, Nov 11, 2016 at 11:51:34AM -0700, Martin Sebor wrote: On 11/11/2016 10:53 AM, Richard Biener wrote: On November 11, 2016 6:34:37 PM GMT+01:00, Martin Sebor wrote: I noticed that variables of signed integer types that are constrained to a s

gcc-7-20161113 is now available

2016-11-13 Thread gccadmin
Snapshot gcc-7-20161113 is now available on ftp://gcc.gnu.org/pub/gcc/snapshots/7-20161113/ 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/trunk revision

DLLTool put wrong hint value in lib archieve (GCC 6.2)

2016-11-13 Thread Rudy
I'm email this, since I can't register in your bug report forum, its because my IP I think. I just want to report that DLLTool put wrong hint value in lib archieve (IDATA6 section). In "make_one_lib_file" function, I see the hint value grab from "{struct}export->hint", instead it should grab from