On Tue, Dec 5, 2017 at 4:00 AM, Martin Jambor wrote:
> On Tue, Dec 05 2017, Martin Jambor wrote:
>> On Tue, Dec 05 2017, Martin Jambor wrote:
>> Hi,
>>
>>> Hi,
>>>
>>> this is a followup to Richi's
>>> https://gcc.gnu.org/ml/gcc-patches/2017-11/msg02396.html to fix PR
>>> 83141. The basic idea
This patch by Tony Reix changes libgo's poller support on AIX to use
poll rather than pollset. This may fixes
https://golang.org/issue/26634. Bootstrapped and ran Go testsuite on
x86_64-pc-linux, not that that proves much. Committed to mainline.
Ian
Index: gcc/go/gofrontend/MERGE
On Tue, Jul 31, 2018 at 05:01:02PM -0500, Bill Schmidt wrote:
> > On Jul 27, 2018, at 4:37 AM, Richard Earnshaw
> > wrote:
> > This patch reworks the existing rs6000_speculation_barrier pattern to
> > work with the new __builtin_sepculation_safe_value() intrinsic. The
> > change is trivial as
On 07/31/2018 09:48 AM, Jakub Jelinek wrote:
On Tue, Jul 31, 2018 at 09:17:52AM -0600, Martin Sebor wrote:
On 07/31/2018 12:38 AM, Jakub Jelinek wrote:
On Mon, Jul 30, 2018 at 09:45:49PM -0600, Martin Sebor wrote:
Even without _FORTIFY_SOURCE GCC diagnoses (some) writes past
the end of
On Sat, Jul 28, 2018 at 1:25 AM, Uros Bizjak wrote:
> On Fri, Jul 27, 2018 at 11:37 AM, Richard Earnshaw
> wrote:
>>
>> This patch adds a speculation barrier for x86, based on my
>> understanding of the required mitigation for that CPU, which is to use
>> an lfence instruction.
>>
>> This patch
On Wed, Jul 25, 2018 at 01:35:23PM -0500, Luis Machado wrote:
> Adjust Falkor's register_sextend cost from 4 to 3. This fixes a testsuite
> failure in gcc.target/aarch64/extend.c:ldr_sxtw where GCC was generating
> a sbfiz instruction rather than a load with sign extension.
>
> No performance
On Wed, Jul 25, 2018 at 01:10:34PM -0500, Luis Machado wrote:
> The adjusted vector costs give Falkor a reasonable boost in performance for FP
> benchmarks (both CPU2017 and CPU2006) and doesn't change INT benchmarks that
> much. About 0.7% for CPU2017 FP and 1.54% for CPU2006 FP.
>
> OK for
On 31/07/18 18:40 +0100, Jonathan Wakely wrote:
On 31/07/18 20:14 +0300, Ville Voutilainen wrote:
On 31 July 2018 at 20:07, Jonathan Wakely wrote:
The solution for PR 77537 causes ambiguities due to the extra copy
assignment operator taking a __nonesuch_no_braces parameter. The copy
and move
The macro definitions in should depend on the same
preprocessor conditions as the original macros in other headers.
Otherwise can define macros that imply the availability of
features that are not actually defined.
This fix is incomplete, as __cpp_lib_filesystem should depend on whether
Here is a new version of my patch to support the Aarch64 SIMD ABI [1]
in GCC. I think this is complete enought to be considered for check
in. I wrote a few new tests and put them in a new gcc.target/torture
directory so they would be run with multiple optimization options. I
also verified that
On Wed, 1 Aug 2018, Bogdan Harjoc wrote:
> So array[0] < component < array[2], which loops (I removed the gdb p
> commands for field_array[1] and so on).
Is the key thing here that you end up with DECL_NAME (field) == NULL_TREE,
but DECL_NAME (field_array[bot]) != NULL_TREE - and in this
On Thu, Jul 26, 2018 at 11:52:15AM -0500, Sam Tebbs wrote:
> > Thanks for making the changes and adding more test cases. I do however
> > see that you are only covering 2 out of 4 new
> > *aarch64_get_lane_zero_extenddi<> patterns. The
> > *aarch64_get_lane_zero_extendsi<> were already
#define foo(a) did it, thanks!
As Joseph suspected, the hang/no hang result depended on the values of
DECL_NAME pointers:
- with #define foo(a) plus the testcase from bugzilla id 86690 and no
-save-temps, the "return s.a" that triggers lookup_field() will find
the sorted field_array containing:
Hi Richard,
I can't ack the patch, but I am happy with it. Thank you for this work!
-- Bill
Bill Schmidt, Ph.D.
STSM, GCC Architect for Linux on Power
IBM Linux Technology Center
wschm...@linux.vnet.ibm.com
> On Jul 27, 2018, at 4:37 AM, Richard Earnshaw
> wrote:
>
>
> This patch reworks
On Fri, Jul 13, 2018 at 04:15:41AM -0500, Richard Sandiford wrote:
> Given a pattern like:
>
> (define_insn "aarch64_frecpe" ...)
>
> the SVE ACLE implementation wants to generate the pattern for a
> particular (non-constant) mode. This patch automatically generates
> helpers to do that,
On Fri, Jul 20, 2018 at 04:37:34AM -0500, Vlad Lazar wrote:
> Hi,
>
> The patch adds implementations for the NEON intrinsics vabsd_s64 and
> vnegd_s64.
>
On Tue, Jul 31, 2018 at 2:43 PM James Greenhalgh
wrote:
>
> On Thu, Jul 12, 2018 at 12:01:09PM -0500, Sudakshina Das wrote:
> > Hi Eric
> >
> > On 27/06/18 12:22, Wilco Dijkstra wrote:
> > > Eric Botcazou wrote:
> > >
> > >>> This test can easily be changed not to use optimize since it doesn't
>
On Wed, Jul 18, 2018 at 12:47:27PM -0500, Richard Sandiford wrote:
> aarch64_float_const_representable_p was still returning false for
> HFmode, so we wouldn't use 16-bit FMOV immediate. E.g. before the
> patch:
>
> __fp16 foo (void) { return 0x1.1p-3; }
>
> gave:
>
>mov w0,
On Thu, Jul 12, 2018 at 12:01:09PM -0500, Sudakshina Das wrote:
> Hi Eric
>
> On 27/06/18 12:22, Wilco Dijkstra wrote:
> > Eric Botcazou wrote:
> >
> >>> This test can easily be changed not to use optimize since it doesn't look
> >>> like it needs it. We really need to tests these builtins
On Tue, Jul 24, 2018 at 05:28:03AM -0500, Tamar Christina wrote:
> Hi All,
>
> This patch cleans up the testsuite when a run is done with stack clash
> protection turned on.
>
> Concretely this switches off -fstack-clash-protection for a couple of tests:
>
> * sve: We don't yet support
On Tue, Jul 24, 2018 at 05:27:05AM -0500, Tamar Christina wrote:
> Hi All,
>
> This patch is a cascade update from having to re-spin the configure patch
> (no# 4 in the series).
>
> This patch enforces that the default guard size for stack-clash protection for
> AArch64 be 64KB unless the user
I can't approve patches but this one seems to be in
the obvious category so I think it could be checked in
without formal approval.
It is however missing a couple of things: 1) a test case,
and 2) a reference to the bug it fixes in the ChangeLog
and in the test.
With that, if no one objects, I
On Tue, 31 Jul 2018, Richard Biener wrote:
Also, when @2 == @0 + (@1+1) then the original condition is true but
((sizetype) @0 - (sizetype) @2 + @1) > (@1 * 2) is not?
(sizetype) @0 - (sizetype) (@0 + @1 + 1) + @1 > @1 * 2
-> -1 > @1 * 2
which is false. So I can't really see how you can
On Tue, Jul 31, 2018 at 12:25 PM, H.J. Lu wrote:
> On Mon, Jul 30, 2018 at 6:16 AM, Richard Biener wrote:
>> On Fri, 27 Jul 2018, Richard Earnshaw wrote:
>>
>>>
>>> This patch defines a new intrinsic function
>>> __builtin_speculation_safe_value. A generic default implementation is
>>> defined
I've merged trunk revision 263114 to the gccgo branch.
Ian
On Tue, Jul 31, 2018 at 8:10 AM, Iain Buclaw wrote:
> On 31 July 2018 at 16:33, Ian Lance Taylor wrote:
>> On Sun, Jul 29, 2018 at 7:50 AM, Iain Buclaw wrote:
>>>
>>> This is really to suppress the default action-if-found for
>>> AC_CHECK_LIBS. Zlib is not a dependency of libbacktrace, and so
On Tue, Jul 31, 2018 at 9:19 AM, Bernd Edlinger
wrote:
> On 07/31/18 16:40, Ian Lance Taylor wrote:
>> On Tue, Jul 31, 2018 at 5:14 AM, Bernd Edlinger
>> wrote:
>>>
>>> could someone please review this patch and check it in into the GO FE?
>>
>> I don't understand why the change is correct, and
On Tue, 31 Jul 2018, Jakub Jelinek wrote:
> On Tue, Jul 31, 2018 at 08:04:58PM +, Joseph Myers wrote:
> > On Tue, 24 Jul 2018, Jakub Jelinek wrote:
> >
> > > Bootstrapped/regtested on x86_64-linux and i686-linux, ok for trunk and
> > > release branches?
> > >
> > > 2018-07-24 Jakub Jelinek
On Tue, Jul 31, 2018 at 08:04:58PM +, Joseph Myers wrote:
> On Tue, 24 Jul 2018, Jakub Jelinek wrote:
>
> > Bootstrapped/regtested on x86_64-linux and i686-linux, ok for trunk and
> > release branches?
> >
> > 2018-07-24 Jakub Jelinek
> >
> > PR c/85704
> > * c-typeck.c
On Tue, 24 Jul 2018, Jakub Jelinek wrote:
> Bootstrapped/regtested on x86_64-linux and i686-linux, ok for trunk and
> release branches?
>
> 2018-07-24 Jakub Jelinek
>
> PR c/85704
> * c-typeck.c (field_decl_cmp): New function.
> (output_pending_init_elements): Use it for
On Tue, 31 Jul 2018, David Malcolm wrote:
> I didn't exhaustively check every callsite to the changed calls; I'm
> assuming that -Wformat during bootstrap has effectively checked that
> for me. Though now I think about it, I note that we use
> HOST_WIDE_INT_PRINT_DEC in many places: is this
On Tue, 31 Jul 2018, Bogdan Harjoc wrote:
> With fresh git sources and contrib/gcc_update the tests pass:
>
> === gcc Summary ===
>
> # of expected passes 133500
> # of expected failures 422
> # of unsupported tests 2104
>
> gcc-build/gcc/xgcc version 9.0.0 20180730 (experimental) (GCC)
>
>
On Mon, 30 Jul 2018, John Ericson wrote:
> That said, it is my tentative understanding that the point of having config-ml
> is to cordon-off all the necessarily-multilib-specific logic so it doesn't
> pollute everything else. When that script isn't run, I think the Makefiles
> already contain
On Mon, Jul 30, 2018 at 6:16 AM, Richard Biener wrote:
> On Fri, 27 Jul 2018, Richard Earnshaw wrote:
>
>>
>> This patch defines a new intrinsic function
>> __builtin_speculation_safe_value. A generic default implementation is
>> defined which will attempt to use the backend pattern
>>
The GCC internal %G directive takes a gcall* argument and prints
the call's inlining stack in diagnostics. The argument type makes
it unsuitable for gimple expressions such as those diagnosed by
-Warray-bounds.
As the first step in adding inlining context to -Warray-bounds
warnings the attached
Attached is a much scaled-down patch that only adds a note
to the -Warray-bounds warnings mentioning the declaration
to which the out-of-bounds index or offset applies.
Printing the inlining context needs a bit more work but
this small improvement can be made independently of it.
On 07/23/2018
On 30/07/18 14:29, Richard Biener wrote:
On Sun, Jul 29, 2018 at 6:27 PM Jozef Lawrynowicz
wrote:
pr45678-2.c ICEs for msp430-elf with -mlarge, because an alignment of
POINTER_SIZE is attempted. POINTER_SIZE with -mlarge is 20-bits, so further
code in the middle-end that expects this to be a
Hi,
Thanks for submitting the patch.
Bogdan Harjoc writes:
> With fresh git sources and contrib/gcc_update the tests pass:
>
> === gcc Summary ===
>
> # of expected passes 133500
> # of expected failures 422
> # of unsupported tests 2104
>
> gcc-build/gcc/xgcc version 9.0.0 20180730
On 31/07/18 20:14 +0300, Ville Voutilainen wrote:
On 31 July 2018 at 20:07, Jonathan Wakely wrote:
The solution for PR 77537 causes ambiguities due to the extra copy
assignment operator taking a __nonesuch_no_braces parameter. The copy
and move assignment operators can be defined as defaulted
On 2018-07-26 01:27 PM, Michael Ploujnikov wrote:
> On 2018-07-24 09:57 AM, Michael Ploujnikov wrote:
>> On 2018-07-20 06:05 AM, Richard Biener wrote:
/* Return a new assembler name for a clone with SUFFIX of a decl named
NAME. */
@@ -521,14 +521,13 @@ tree
On 31 July 2018 at 20:07, Jonathan Wakely wrote:
> The solution for PR 77537 causes ambiguities due to the extra copy
> assignment operator taking a __nonesuch_no_braces parameter. The copy
> and move assignment operators can be defined as defaulted to meet the
> semantics required by the
I've committed this patch which contains all of the remaining
goacc_parlevel bug fixes present in trunk to og8.
The goal of the goacc parlevel changes is replace the use of inline ptx
code with builtin functions so that the certain OpenACC execution tests
that exercise the execution model can be
Hi Paul,
2018-07-31 14:06 GMT+02:00 Paul Richard Thomas :
> Daniel Celis Garza and Damian Rouson have developed a runtime library
> and include file for the TS 29113 and F2018 C descriptors.
> https://github.com/sourceryinstitute/ISO_Fortran_binding
>
> The ordering of types is different to the
The solution for PR 77537 causes ambiguities due to the extra copy
assignment operator taking a __nonesuch_no_braces parameter. The copy
and move assignment operators can be defined as defaulted to meet the
semantics required by the standard.
In order to preserve ABI compatibility (specifically
On 07/31/2018 04:04 PM, Richard Biener wrote:
On Sat, 28 Jul 2018, Andris Pavenis wrote:
On 07/27/2018 11:51 PM, DJ Delorie wrote:
Richard Biener writes:
DJ, did you ever run the testsuite with a configuration that has LTO
enabled? I don't see any djgpp results posted to gcc-testresults.
I've committed this patch to og8 which backports the first of Tom's
goacc_parlevel patches from mainline. I'll post of a followup patch
which contains various bug fixes. I believe that this patch was
originally introduced in PR82428, or at least it resolves that PR.
Cesar
[og8] Add
On 07/31/18 16:40, Ian Lance Taylor wrote:
> On Tue, Jul 31, 2018 at 5:14 AM, Bernd Edlinger
> wrote:
>>
>> could someone please review this patch and check it in into the GO FE?
>
> I don't understand why the change is correct, and you didn't explain
> it. Go strings are not NUL terminated.
Way back in the GCC 5 days when support for OpenACC was in its infancy,
we used to rely on having various GOACC_ thread functions in the runtime
to implement the execution model, or there lack of (that version of GCC
only supported vector level parallelism). However, beginning with GCC 6,
those
Hi Richard,
The 07/31/2018 11:21, Richard Biener wrote:
> On Tue, 31 Jul 2018, Tamar Christina wrote:
>
> > Ping
> >
> > > -Original Message-
> > > From: gcc-patches-ow...@gcc.gnu.org
> > > On Behalf Of Tamar Christina
> > > Sent: Tuesday, July 24, 2018 17:34
> > > To: Richard Biener
On Tue, Jul 31, 2018 at 09:17:52AM -0600, Martin Sebor wrote:
> On 07/31/2018 12:38 AM, Jakub Jelinek wrote:
> > On Mon, Jul 30, 2018 at 09:45:49PM -0600, Martin Sebor wrote:
> > > Even without _FORTIFY_SOURCE GCC diagnoses (some) writes past
> > > the end of subobjects by string functions. With
From: Andreas Krebbel
gcc/ChangeLog:
2018-07-31 Andreas Krebbel
* config/s390/s390.c (s390_expand_setmem): Make the unrolling to
depend on whether prefetch instructions will be emitted or not.
Use TARGET_SETMEM_PFD for checking whether prefetch instructions
On 31/07/18 14:57, Segher Boessenkool wrote:
> Hi Christophe,
>
> On Tue, Jul 31, 2018 at 02:34:06PM +0200, Christophe Lyon wrote:
>> Since this was committed, I've noticed regressions
>> on aarch64:
>> FAIL: gcc.dg/zero_bits_compound-1.c scan-assembler-not \\(and:
>
> This went from
>
On Tue, Jul 31, 2018 at 5:34 PM David Malcolm wrote:
>
> On Tue, 2018-07-31 at 14:53 +0200, Richard Biener wrote:
> > On Fri, Jul 27, 2018 at 11:48 PM David Malcolm
> > wrote:
> > >
> > > With the addition of optinfo, the various dump_* calls had three
> > > parts:
> > > - optionally print to
On Tue, 2018-07-31 at 14:53 +0200, Richard Biener wrote:
> On Fri, Jul 27, 2018 at 11:48 PM David Malcolm
> wrote:
> >
> > With the addition of optinfo, the various dump_* calls had three
> > parts:
> > - optionally print to dump_file
> > - optionally print to alt_dump_file
> > - optionally make
Just teasing things apart a bit more in this function so I can add
vec/vsx code generation without making it enormous and
incomprehensible.
Bootstrap/regtest passes on powerpc64le, ok for trunk?
Thanks,
Aaron
2018-07-31 Aaron Sawdey
* config/rs6000/rs6000-string.c
At present, libgomp is using CUDA unified memory only as a buffer pass
to the struct containing the pointers to the data mappings to the
offloaded functions. I'm not sure why unified memory is needed here if
it is still being managed explicitly by the driver.
This patch removes the use of CUDA
On 07/31/2018 12:38 AM, Jakub Jelinek wrote:
On Mon, Jul 30, 2018 at 09:45:49PM -0600, Martin Sebor wrote:
Even without _FORTIFY_SOURCE GCC diagnoses (some) writes past
the end of subobjects by string functions. With _FORTIFY_SOURCE=2
it calls abort. This is the default on popular
Hi Richard,
Ah yes, you are absolutely right. I will sit on it for a bit and do
the interchange at the descriptor conversion stage for now.
Thanks
Paul
On Tue, 31 Jul 2018 at 15:57, Richard Biener wrote:
>
> On Tue, Jul 31, 2018 at 2:07 PM Paul Richard Thomas
> wrote:
> >
> > Daniel Celis
Description:
* This patch optimizes the time required for loading XCOFF data.
Tests:
* AIX: Build: SUCCESS
- build made by means of gmake on AIX.
ChangeLog:
* xcoff.c: Optimize loading of XCOFF data.
Cordialement,
Tony Reix
tony.r...@atos.net
ATOS / Bull SAS
ATOS Expert
This is an old patch which removes the struct map from the nvptx plugin.
I believe at one point this was supposed to be used to manage async data
mappings, but in practice that never worked out.
Is this OK for trunk? I bootstrapped and regtested on x86_64 with nvptx
offloading.
Thanks,
Cesar
On 31 July 2018 at 16:33, Ian Lance Taylor wrote:
> On Sun, Jul 29, 2018 at 7:50 AM, Iain Buclaw wrote:
>>
>> This is really to suppress the default action-if-found for
>> AC_CHECK_LIBS. Zlib is not a dependency of libbacktrace, and so it
>> shouldn't be added to LIBS. When looking at the
Instead of repeating all the old headers for every new standard I've
changed the docs to only list the new headers for each standard.
* doc/xml/manual/test.xml: Improve documentation on writing tests for
newer standards.
* doc/xml/manual/using.xml: Document all headers
Richard Biener writes:
> On Tue, Jul 24, 2018 at 12:01 PM Richard Sandiford
> wrote:
>>
>> This patch changes SLP_TREE_SCALAR_STMTS from a vec to
>> a vec. It's longer than the previous conversions
>> but mostly mechanical.
>
> OK. I don't remember exactly but vect_external_def SLP nodes have
The attached patch teaches libgomp how to use the CUDA thread occupancy
calculator built into the CUDA driver. Despite both being based off the
CUDA thread occupancy spreadsheet distributed with CUDA, the built in
occupancy calculator differs from the occupancy calculator in og8 in two
key ways.
On Tue, Jul 31, 2018 at 2:07 PM Paul Richard Thomas
wrote:
>
> Daniel Celis Garza and Damian Rouson have developed a runtime library
> and include file for the TS 29113 and F2018 C descriptors.
> https://github.com/sourceryinstitute/ISO_Fortran_binding
>
> The ordering of types is different to
* include/ext/pointer.h [__cplusplus >= 201103L]
(_Pointer_adapter::operator bool): Add explicit conversion operator
to replace safe bool idiom.
Tested powerpc64le-linux, committed to trunk.
commit 791062941cf5c4b93153bfd10d5bb9b0ac78d301
Author: Jonathan Wakely
Date:
On 07/31/2018 07:38 AM, Jason Merrill wrote:
On Tue, Jul 31, 2018 at 9:51 AM, Martin Sebor wrote:
The middle-end contains code to determine the lengths of constant
character arrays initialized by string literals. The code is used
in a number of optimizations and warnings.
However, the code
On Tue, Jul 31, 2018 at 5:14 AM, Bernd Edlinger
wrote:
>
> could someone please review this patch and check it in into the GO FE?
I don't understand why the change is correct, and you didn't explain
it. Go strings are not NUL terminated. Go strings always have an
associated length.
Ian
I noticed that the switch code on PowerPC little endian systems (with medium
code mode) did not follow the ABI in terms of page 69:
Table 2.36. Position-Independent Switch Code for Small/Medium Models
(preferred, with TOC-relative addressing)
The code we currently generate is:
On Mon, Jul 23, 2018 at 8:50 PM, Richard Biener
wrote:
> On Mon, Jul 23, 2018 at 12:28 PM Jakub Jelinek wrote:
>>
>> On Mon, Jul 23, 2018 at 12:17:42PM +0200, Richard Biener wrote:
>> > > Bootstrapped/regtested on x86_64-linux.
>> >
>> > Thanks for working on this. I wonder if we can completely
On Tue, Jul 31, 2018 at 4:21 PM Richard Biener
wrote:
>
> On Tue, Jul 31, 2018 at 4:19 PM David Malcolm wrote:
> >
> > On Tue, 2018-07-31 at 15:03 +0200, Richard Biener wrote:
> > > On Fri, Jul 27, 2018 at 11:49 PM David Malcolm
> > > wrote:
> > > >
> > > > This patch converts dump_print and
On Sun, Jul 29, 2018 at 7:50 AM, Iain Buclaw wrote:
>
> This is really to suppress the default action-if-found for
> AC_CHECK_LIBS. Zlib is not a dependency of libbacktrace, and so it
> shouldn't be added to LIBS. When looking at the check, saw that could
> remove the test for
On Tue, Jul 31, 2018 at 4:19 PM David Malcolm wrote:
>
> On Tue, 2018-07-31 at 15:03 +0200, Richard Biener wrote:
> > On Fri, Jul 27, 2018 at 11:49 PM David Malcolm
> > wrote:
> > >
> > > This patch converts dump_print and dump_printf_loc from using
> > > printf (and thus ATTRIBUTE_PRINTF) to
On Tue, 2018-07-31 at 15:03 +0200, Richard Biener wrote:
> On Fri, Jul 27, 2018 at 11:49 PM David Malcolm
> wrote:
> >
> > This patch converts dump_print and dump_printf_loc from using
> > printf (and thus ATTRIBUTE_PRINTF) to using a new pretty-printer
> > based on pp_format, which supports
On Mon, Jul 30, 2018 at 9:01 PM, Jakub Jelinek wrote:
> Seems what is considered an aggregate type keeps changing in every single
> C++ version.
Indeed :/
> Bootstrapped/regtested on x86_64-linux and i686-linux, ok for trunk?
This is OK. I think we could also use a -Wc++2a-compat warning, and
On Tue, Jul 31, 2018 at 05:39:37AM -0700, H.J. Lu wrote:
> For
>
> ---
> #define N 16
> float f[N];
> double d[N];
> int n[N];
>
> __attribute__((noinline)) void
> f3 (void)
> {
> int i;
> for (i = 0; i < N; i++)
> d[i] = f[i];
> }
> ---
>
> r263067 improved -O3 -mavx2 -mtune=generic
On Tue, 2018-07-31 at 14:50 +0200, Richard Biener wrote:
> On Fri, Jul 27, 2018 at 11:47 PM David Malcolm
> wrote:
> >
> > This patch kit converts dump_print and dump_printf_loc from using
> > fprintf etc internally to using a new pretty-printer
> > based on pp_format, which supports formatting
Hi Christophe,
On Tue, Jul 31, 2018 at 02:34:06PM +0200, Christophe Lyon wrote:
> Since this was committed, I've noticed regressions
> on aarch64:
> FAIL: gcc.dg/zero_bits_compound-1.c scan-assembler-not \\(and:
This went from
and w0, w0, 255
lsl w1, w0, 8
orr
On Tue, Jul 31, 2018 at 9:51 AM, Martin Sebor wrote:
> The middle-end contains code to determine the lengths of constant
> character arrays initialized by string literals. The code is used
> in a number of optimizations and warnings.
>
> However, the code is unable to deal with constant arrays
Hi Thomas,
On 25/07/18 14:28, Thomas Preudhomme wrote:
Hi Kyrill,
Using memory_operand worked, the issues I encountered when using it in
earlier versions of the patch must have been due to the missing test
on address_operand in the preparation statements which I added later.
Please find an
OK.
On Tue, Jul 31, 2018 at 7:22 PM, Richard Biener wrote:
> On Mon, 30 Jul 2018, Tom de Vries wrote:
>
>> Hi,
>>
>> Consider test.C compiled at -O0 -g:
>> ...
>> class string {
>> public:
>> string (const char *p) { this->p = p ; }
>> string (const string ) { this->p = s.p; }
>>
>> private:
On Tue, Jul 31, 2018 at 02:56:29PM +0200, Richard Biener wrote:
> On Fri, Jul 27, 2018 at 11:48 PM David Malcolm wrote:
> >
> > The format_char_info tables in c-format.c for our own formats contain
> > a lot of repetition.
> >
> > This patch adds a macro to express the conversion specifiers
On Sat, 28 Jul 2018, Andris Pavenis wrote:
> On 07/27/2018 11:51 PM, DJ Delorie wrote:
> > Richard Biener writes:
> > > DJ, did you ever run the testsuite with a configuration that has LTO
> > > enabled? I don't see any djgpp results posted to gcc-testresults.
> > > Quick googling doesn't yield
On Fri, Jul 27, 2018 at 11:49 PM David Malcolm wrote:
>
> This patch converts dump_print and dump_printf_loc from using
> printf (and thus ATTRIBUTE_PRINTF) to using a new pretty-printer
> based on pp_format, which supports formatting middle-end types.
>
> In particular, the following codes are
Christophe Lyon writes:
> On Mon, 30 Jul 2018 at 18:09, Segher Boessenkool
> wrote:
>>
>> On Tue, Jul 24, 2018 at 05:18:41PM +, Segher Boessenkool wrote:
>> > This patch allows combine to combine two insns into two. This helps
>> > in many cases, by reducing instruction path length, and
On Fri, Jul 27, 2018 at 11:48 PM David Malcolm wrote:
>
> The format_char_info tables in c-format.c for our own formats contain
> a lot of repetition.
>
> This patch adds a macro to express the conversion specifiers implemented
> within pp_format, making it clearer which are custom ones added by
On Fri, Jul 27, 2018 at 11:48 PM David Malcolm wrote:
>
> With the addition of optinfo, the various dump_* calls had three parts:
> - optionally print to dump_file
> - optionally print to alt_dump_file
> - optionally make an optinfo_item and add it to the pending optinfo,
> creating it for
On Fri, Jul 27, 2018 at 11:48 PM David Malcolm wrote:
>
> This patch removes some duplicated code in dumpfile.c by
> reimplementing the various dump_foo_loc calls in terms of dump_foo.
OK.
Richard.
> gcc/ChangeLog:
> * dump-context.h (dump_context::dump_loc): New decl.
> *
On Fri, Jul 27, 2018 at 11:47 PM David Malcolm wrote:
>
> This patch kit converts dump_print and dump_printf_loc from using
> fprintf etc internally to using a new pretty-printer
> based on pp_format, which supports formatting middle-end types.
>
> In particular, the following codes are
On Tue, Jul 24, 2018 at 3:47 PM Martin Jambor wrote:
>
> Hi,
>
> I'd like to propose again a new variant of a fix that I sent here in
> November (https://gcc.gnu.org/ml/gcc-patches/2017-10/msg00881.html) that
> avoids store-to-load forwarding stalls in the ImageMagick benchmark by
> expanding
On Wed, Jul 25, 2018 at 1:28 AM, Richard Biener
wrote:
> On Tue, Jul 24, 2018 at 7:18 PM Segher Boessenkool
> wrote:
>>
>> This patch allows combine to combine two insns into two. This helps
>> in many cases, by reducing instruction path length, and also allowing
>> further combinations to
Hi Segher,
On 31/07/18 13:14, Segher Boessenkool wrote:
Hi Kyrill,
As before, untested. Is this okay for trunk, or will you handle it
yourself (or will someone else do it?)
This is ok.
Thanks,
Kyrill
Segher
2018-07-31 Segher Boessenkool
gcc/testsuite/
PR target/86640
On Mon, 30 Jul 2018 at 18:09, Segher Boessenkool
wrote:
>
> On Tue, Jul 24, 2018 at 05:18:41PM +, Segher Boessenkool wrote:
> > This patch allows combine to combine two insns into two. This helps
> > in many cases, by reducing instruction path length, and also allowing
> > further
On 07/30/18 15:03, Richard Biener wrote:
> On Mon, 30 Jul 2018, Bernd Edlinger wrote:
>
>> Hi,
>>
>> this is how I would like to handle the over length strings issue in the C FE.
>> If the string constant is exactly the right length and ends in one explicit
>> NUL character, shorten it by one
Hi,
could someone please review this patch and check it in into the GO FE?
Thanks
Bernd.
2018-07-31 Bernd Edlinger
* go-gcc.cc (Gcc_backend::string_constant_expression): Make string
literal properly NUL terminated.
diff -pur gcc/go/go-gcc.cc gcc/go/go-gcc.cc
--- gcc/go/go-gcc.cc
Hi Kyrill,
As before, untested. Is this okay for trunk, or will you handle it
yourself (or will someone else do it?)
Segher
2018-07-31 Segher Boessenkool
gcc/testsuite/
PR target/86640
* gcc.target/arm/pr86640.c: New testcase.
---
gcc/testsuite/gcc.target/arm/pr86640.c
Hi!
This fixes a couple STRING_CST that are not explicitly NUL terminated.
These were caught in a new check in varasm.c I am currently working on.
Having a NUL terminated string does not change the binary output, but it
makes things easier for he middle-end.
Bootstrapped and reg-tested on
Daniel Celis Garza and Damian Rouson have developed a runtime library
and include file for the TS 29113 and F2018 C descriptors.
https://github.com/sourceryinstitute/ISO_Fortran_binding
The ordering of types is different to the current 'bt' enum in
libgfortran.h. This patch interchanges
On Tue, Jul 24, 2018 at 12:11 PM Richard Sandiford
wrote:
>
> This patch removes the stmt_vec_info wrapper class added near the
> beginning of the series and turns stmt_vec_info back into a typedef.
>
OK. For the whole series now if I didn't miss anything...
Richard.
> 2018-07-24 Richard
On Tue, Jul 24, 2018 at 12:11 PM Richard Sandiford
wrote:
>
> Unlike the old vinfo_for_stmt, vec_info::lookup_stmt can cope with
> any statement, so there's no need to check beforehand that the statement
> is part of the vectorisable region. This means that there are no longer
> any calls to
1 - 100 of 137 matches
Mail list logo
