Re: [PATCH v2] libitm: sh: avoid absolute relocation in shared library (PR 86712)

2018-08-04 Thread Oleg Endo
On Fri, 2018-08-03 at 14:54 -0600, Jeff Law wrote: > On 07/28/2018 07:04 AM, slyfox.inbox.ru via gcc-patches wrote: > > > > From: Sergei Trofimovich > > > > Cc: Andreas Schwab > > Cc: Torvald Riegel > > Cc: Alexandre Oliva > > Cc: Oleg Endo > > Cc: Kaz Kojima > > Signed-off-by: Sergei Trofi

Re: [PATCH] i386: Always set cfun->machine->max_used_stack_alignment

2018-08-04 Thread Uros Bizjak
On Fri, Aug 3, 2018 at 12:55 AM, H.J. Lu wrote: > We should always set cfun->machine->max_used_stack_alignment if the > maximum stack slot alignment may be greater than 64 bits. > > Tested on i686 and x86-64. OK for master and backport for GCC 8? Can you explain why 64 bits, and what this value

Re: [PATCH] [Ada] Make middle-end string literals NUL terminated

2018-08-04 Thread Bernd Edlinger
Hi Olivier, I think I like your idea a lot, it should be highly useful for Fortran and GO as well. Would somthing something like this (untested patch) work for you on top of my patch series. It makes use of the zero-termination properties of STRING_CSTs, that the other patch ensures. I have

Re: [PATCH][2/4] Add rev_post_order_and_mark_dfs_back_seme

2018-08-04 Thread Bernhard Reutner-Fischer
On Wed, 1 Aug 2018 at 16:31, Richard Biener wrote: > --- a/gcc/cfganal.c > +++ b/gcc/cfganal.c > @@ -1057,6 +1057,119 @@ pre_and_rev_post_order_compute (int *pre_order, int > *rev_post_order, >return pre_order_num; > } > > +/* Unline pre_and_rev_post_order_compute we fill rev_post_order back

patch to bug #86829

2018-08-04 Thread Giuliano Augusto Faulin Belinassi
Closes bug #86829 Description: Adds substitution rules for both sin(atan(x)) and cos(atan(x)). These formulas are replaced by x / sqrt(x*x + 1) and 1 / sqrt(x*x + 1) respectively, providing up to 10x speedup. This identity can be proved mathematically. Changelog: 2018-08-03 Giuliano Belinassi

Re: [PATCH] i386: Always set cfun->machine->max_used_stack_alignment

2018-08-04 Thread H.J. Lu
On Sat, Aug 4, 2018 at 3:42 AM, Uros Bizjak wrote: > On Fri, Aug 3, 2018 at 12:55 AM, H.J. Lu wrote: >> We should always set cfun->machine->max_used_stack_alignment if the >> maximum stack slot alignment may be greater than 64 bits. >> >> Tested on i686 and x86-64. OK for master and backport for

[Patch, Fortran, F08] PR 45521: GENERIC resolution with ALLOCATABLE/POINTER and PROCEDURE

2018-08-04 Thread Janus Weil
Hi all, this patch should finally fix up the last wrinkles of PR 45521, which deals with disambiguating specific procedures in a generic interface via the pointer/allocatable attributes of the arguments (legal in F08). For 'ordinary' generic interfaces this already works (cf. 'generic_corresponde

[PATCH] Handle not explicitly zero terminated strings in merge sections

2018-08-04 Thread Bernd Edlinger
Hi! This patch is inspired by Olivier's feedback to my previous patch on the zero-termination of Ada STRING_CST. The idea is that strings that do not have embedded nul characters _and_ do not happen to be zero-terminated in the DECL_UNIT_SIZE, are currently not in the merge string sections. To

Re: [PATCH] Handle not explicitly zero terminated strings in merge sections

2018-08-04 Thread Bernd Edlinger
Again, with patch On 08/04/18 17:43, Bernd Edlinger wrote: > Hi! > > > This patch is inspired by Olivier's feedback to my previous patch on the > zero-termination of Ada STRING_CST. > > The idea is that strings that do not have embedded nul characters _and_ > do not happen to be zero-termin

Re: [testsuite, committed] Use relative line numbers in gcc.dg/guality

2018-08-04 Thread Andreas Schwab
On Jul 09 2018, Tom de Vries wrote: > this patches uses relative line numbers in gcc.dg/guality where obvious: > either the relative line number is '.', '.-1' or '.+1', or adjacent to > another obvious case. This introduced a lot of test names that are no longer unique. gcc.dg/guality/csttest.c

Re: [PATCH] Handle not explicitly zero terminated strings in merge sections

2018-08-04 Thread Bernd Edlinger
Aehm, I forgot the Fortran FE patch which is also a pre-condition (at least for building with all languages): [PATCH] Create internally nul terminated string literals in fortan FE https://gcc.gnu.org/ml/fortran/2018-08/msg0.html Thanks Bernd. On 08/04/18 17:44, Bernd Edlinger wrote: > Agai

Re: dejagnu version update?

2018-08-04 Thread Bernhard Reutner-Fischer
On Tue, 16 May 2017 at 21:08, Mike Stump wrote: > > On May 16, 2017, at 5:16 AM, Jonathan Wakely wrote: > > The change I care about in 1.5.3 > > So, we haven't talked much about the version people want most. If we update, > might as well get something that more people care about. 1.5.3 is in u

Remove duplicate test

2018-08-04 Thread Andreas Schwab
The test for type:cvip was being run twice. Committed as obvious. Andreas. * gcc.dg/guality/const-volatile.c: Remove duplicate test "type:cvip". diff --git a/gcc/testsuite/gcc.dg/guality/const-volatile.c b/gcc/testsuite/gcc.dg/guality/const-volatile.c index 3bfca0d14d..21f84b5c

[PATCH] assume sprintf formatting of wide characters may fail (PR 86853)

2018-08-04 Thread Martin Sebor
The sprintf handling of wide characters neglects to consider that calling the function may fail due to a conversion error (when the wide character is invalid or not representable in the current locale). The handling also misinterprets the POSIX %S wide string directive as a plain narrow %s and do

Re: [PATCH] i386: Always set cfun->machine->max_used_stack_alignment

2018-08-04 Thread Uros Bizjak
On Sat, Aug 4, 2018 at 3:59 PM, H.J. Lu wrote: > On Sat, Aug 4, 2018 at 3:42 AM, Uros Bizjak wrote: >> On Fri, Aug 3, 2018 at 12:55 AM, H.J. Lu wrote: >>> We should always set cfun->machine->max_used_stack_alignment if the >>> maximum stack slot alignment may be greater than 64 bits. >>> >>> Tes

Re: [PATCH] i386: Always set cfun->machine->max_used_stack_alignment

2018-08-04 Thread H.J. Lu
On Sat, Aug 4, 2018 at 12:09 PM, Uros Bizjak wrote: > On Sat, Aug 4, 2018 at 3:59 PM, H.J. Lu wrote: >> On Sat, Aug 4, 2018 at 3:42 AM, Uros Bizjak wrote: >>> On Fri, Aug 3, 2018 at 12:55 AM, H.J. Lu wrote: We should always set cfun->machine->max_used_stack_alignment if the maximum st

[committed, libgomp, nvptx, --without-cuda-driver] Don't use system cuda driver

2018-08-04 Thread Tom de Vries
Hi, Using libgomp configure option --with-cuda-driver= we can indicate what cuda driver to use to build the libgomp nvptx plugin. Without such an option, the system cuda driver is used, if available. If not availabe, a dlopen interface is used instead. However, when we use --without-cuda-driver

Re: [PATCH,nvptx] Use CUDA driver API to select default runtime launch, geometry

2018-08-04 Thread Tom de Vries
On 08/03/2018 05:37 PM, Cesar Philippidis wrote: >> But I still see no rationale why blocks is used here, and I wonder >> whether something like num_gangs = grids * 64 would give similar results. > My original intent was to keep the load proportional to the block size. > So, in the case were a blo

Re: [PATCH] Make strlen range computations more conservative

2018-08-04 Thread Martin Sebor
On 08/03/2018 01:43 AM, Jakub Jelinek wrote: On Thu, Aug 02, 2018 at 09:59:13PM -0600, Martin Sebor wrote: If I call this with foo (2, 1), do you still claim it is not valid C? String functions like strlen operate on character strings stored in character arrays. Calling strlen (&s[1]) is inva

[committed, testsuite, guality] Use absolute line number in pass/fail line

2018-08-04 Thread Tom de Vries
On Sat, Aug 04, 2018 at 05:45:59PM +0200, Andreas Schwab wrote: > On Jul 09 2018, Tom de Vries wrote: > > > this patches uses relative line numbers in gcc.dg/guality where obvious: > > either the relative line number is '.', '.-1' or '.+1', or adjacent to > > another obvious case. > > This intro

Re: [PATCH] i386: Always set cfun->machine->max_used_stack_alignment

2018-08-04 Thread Uros Bizjak
On Sat, Aug 4, 2018 at 9:49 PM, H.J. Lu wrote: > On Sat, Aug 4, 2018 at 12:09 PM, Uros Bizjak wrote: >> On Sat, Aug 4, 2018 at 3:59 PM, H.J. Lu wrote: >>> On Sat, Aug 4, 2018 at 3:42 AM, Uros Bizjak wrote: On Fri, Aug 3, 2018 at 12:55 AM, H.J. Lu wrote: > We should always set cfun->ma

Re: [PATCH] Make strlen range computations more conservative

2018-08-04 Thread Martin Sebor
On 08/03/2018 01:00 AM, Jeff Law wrote: On 07/24/2018 05:18 PM, Bernd Edlinger wrote: On 07/24/18 23:46, Jeff Law wrote: On 07/24/2018 01:59 AM, Bernd Edlinger wrote: Hi! This patch makes strlen range computations more conservative. Firstly if there is a visible type cast from type A to B be

Re: [PATCH] adjust sprintf range for AIX QNaN output (PR 86571)

2018-08-04 Thread Martin Sebor
On 08/02/2018 01:46 PM, Martin Sebor wrote: The recently added test gcc.dg/torture/builtin-sprintf.c to verify that the sprintf result computed by GCC matches libc's for Infinity and NaN has been failing on AIX which formats NaN as either QNaN or SNaN, contrary to C/POSIX requirements. The attac

Re: [PATCH] adjust sprintf range for AIX QNaN output (PR 86571)

2018-08-04 Thread David Edelsohn
On Sat, Aug 4, 2018, 18:19 Martin Sebor wrote: > On 08/02/2018 01:46 PM, Martin Sebor wrote: > > The recently added test gcc.dg/torture/builtin-sprintf.c > > to verify that the sprintf result computed by GCC matches > > libc's for Infinity and NaN has been failing on AIX which > > formats NaN as

Re: [PATCH] adjust sprintf range for AIX QNaN output (PR 86571)

2018-08-04 Thread Martin Sebor
On 08/04/2018 04:25 PM, David Edelsohn wrote: On Sat, Aug 4, 2018, 18:19 Martin Sebor mailto:mse...@gmail.com>> wrote: On 08/02/2018 01:46 PM, Martin Sebor wrote: > The recently added test gcc.dg/torture/builtin-sprintf.c > to verify that the sprintf result computed by GCC matches

Re: [PATCH] i386: Always set cfun->machine->max_used_stack_alignment

2018-08-04 Thread H.J. Lu
On Sat, Aug 04, 2018 at 11:48:15PM +0200, Uros Bizjak wrote: > On Sat, Aug 4, 2018 at 9:49 PM, H.J. Lu wrote: > > On Sat, Aug 4, 2018 at 12:09 PM, Uros Bizjak wrote: > >> On Sat, Aug 4, 2018 at 3:59 PM, H.J. Lu wrote: > >>> On Sat, Aug 4, 2018 at 3:42 AM, Uros Bizjak wrote: > On Fri, Aug 3

Re: [PATCH] Make strlen range computations more conservative

2018-08-04 Thread Bernd Edlinger
On 08/04/18 23:56, Martin Sebor wrote: > On 08/03/2018 01:00 AM, Jeff Law wrote: >> On 07/24/2018 05:18 PM, Bernd Edlinger wrote: >>> On 07/24/18 23:46, Jeff Law wrote: On 07/24/2018 01:59 AM, Bernd Edlinger wrote: > Hi! > > This patch makes strlen range computations more conservat

Re: [PATCH] Make strlen range computations more conservative

2018-08-04 Thread Bernd Edlinger
On 08/04/18 22:52, Martin Sebor wrote: > On 08/03/2018 01:43 AM, Jakub Jelinek wrote: >> On Thu, Aug 02, 2018 at 09:59:13PM -0600, Martin Sebor wrote: If I call this with foo (2, 1), do you still claim it is not valid C? >>> >>> String functions like strlen operate on character strings stored