Hi Segher,
On 30/07/18 18:37, Segher Boessenkool wrote:
On Mon, Jul 30, 2018 at 03:55:30PM +0100, Kyrill Tkachov wrote:
Hi Segher,
On 30/07/18 14:14, Segher Boessenkool wrote:
In arm_block_set_aligned_vect 8-bit constants are generated as zero-
extended const_ints, not sign-extended as requir
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 &s) { this->p = s.p; }
>
> private:
> const char *p;
> };
>
> class foo {
> public:
> foo (string dir
> Hi.
>
> This is implementation of new built-in that can be used for more fine
> tweaking of probability. Micro benchmark is attached as part of the PR.
>
> Patch can bootstrap on ppc64le-redhat-linux and survives regression tests.
>
> Ready to be installed?
It reasonale to me to add the fatur
> Hi.
>
> Following patch implements new predictors that annotates malloc-like
> functions.
> These almost every time return a non-null value.
>
> Patch can bootstrap on ppc64le-redhat-linux and survives regression tests.
>
> Ready to be installed?
> Martin
>
> gcc/ChangeLog:
>
> 2018-07-26
Hi all,
This patch captures the case where an unnecessary uxtw instruction is
generated
after a bfxil instruction when in SI mode, and stops it from being
generated.
Note that this depends on my previous patch submission
(https://gcc.gnu.org/ml/gcc-patches/2018-07/msg01148.html).
For example:
Ping 😊
> -Original Message-
> From: gcc-patches-ow...@gcc.gnu.org
> On Behalf Of Tamar Christina
> Sent: Monday, July 23, 2018 17:52
> To: gcc-patches@gcc.gnu.org
> Cc: nd ; Ramana Radhakrishnan
> ; Richard Earnshaw
> ; ni...@redhat.com; Kyrylo Tkachov
>
> Subject: [PATCH][GCC][Arm] Clea
Ping 😊
> -Original Message-
> From: Thomas Preudhomme
> Sent: Thursday, July 26, 2018 12:29
> To: Tamar Christina
> Cc: gcc-patches@gcc.gnu.org; nd ; Ramana Radhakrishnan
> ; Richard Earnshaw
> ; ni...@redhat.com; Kyrylo Tkachov
>
> Subject: Re: [PATCH][GCC][Arm] Fix subreg crash in dif
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
> Cc: gcc-patches@gcc.gnu.org; nd ; l...@redhat.com;
> i...@airs.com; amo...@gmail.com; berg...@vnet.ibm.com
> Subject: Re: [PATCH][G
On Mon, Jul 30, 2018 at 10:16 PM Martin Sebor wrote:
>
> The enhanced handling of MEM_REFs in -Warray-bounds assumes
> the object from whose address an offset is being computed has
> a complete type. Since the size of such objects isn't known,
> whether the offset (or index) from its beginning is
This patch fixes a bug in which if "pragma Default_Storage_Pool (null);"
is given, then a build-in-place function will get an incorrect error
message "allocation from empty storage pool" even though there is no
such allocation in the source program.
Tested on x86_64-pc-linux-gnu, committed on trun
In GNATprove we used to store a variant of cross-reference information in
the ALI file in lines that started with an 'F' letter. This is no longer
the case, so the letter can be returned to the pool of unused prefixes.
Tested on x86_64-pc-linux-gnu, committed on trunk
2018-07-31 Piotr Trojanek
This patch suppresses a spurious warning on the use of a 64-bit modular type
in a quantified expression, where the range of iteration will include a bound
that appears larger than the run-time representation of Universal_Integer'last.
Tested on x86_64-pc-linux-gnu, committed on trunk
2018-07-31
High-level wrappers are easier to read. This change came up while reading
some code related to GNATprove, but then uniformly applied to the entire
frontend. For the few remaining membership tests that could be replaced
by Is_Formal it is not obvious whether the high-level routine makes the
code bet
When compiling with an assertion-enabled compiler, Assert_Failure can be
raised when expanded an extended_return_statement whose enclosing scope
is not a function (such as when it's a block_statement). The simple fix
is to change the Assert to test Current_Subprogram rather than Current_Scope.
Thre
This patch modifies the expansion of stand-alone subprogram bodies that appear
in the body of a protected type to properly associate aspects and pragmas to
the newly created spec for the subprogram body. As a result, the annotations
are properly associated with the initial declaration of the subpro
This patch corrects an issue whereby objects of a record type with a
representation clause which are overlain by address would fail to get
assigned values properly when one or both of said objects were marked
volatile.
Tested on x86_64-pc-linux-gnu, committed on trunk
2018-07-31 Justin Squirek
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)
I wasn't able to reduce the input to avoid including and as
it on
The alignment of the couple of types from System.OS_Interface was wrongly
set to 4 (32-bit) instead of 8 (64-bit) in 32-bit mode.
Tested on x86_64-pc-linux-gnu, committed on trunk
2018-07-31 Eric Botcazou
gcc/ada/
* libgnarl/s-osinte__solaris.ads (upad64_t): New private type.
This patch fixes a spurious compiler error on a call to a protected
operation whose profile includes a defaulted in-parameter that is a call
to another protected function of the same object.
Tested on x86_64-pc-linux-gnu, committed on trunk
2018-07-31 Ed Schonberg
gcc/ada/
* exp_ch6.
This patch corrects an issue whereby building a multi-unit compilation with
missing sources resulted in a cryptic "code generation" error instead of the
appropriate file not found error.
-- Source --
-- main.adb
with Types;
procedure Main is
begin
null;
end;
-- ty
This patch modifies call resolution to recognize when the designated type of
an access-to-subprogram requires secondary stack management, and establish
the proper transient block.
-- Source --
-- leak7.adb
procedure Leak7 is
Max_Iterations : constant := 10_000;
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
> > Cc: gcc-patches@gcc.gnu.org; nd ; l...@redhat.com;
> > i...@airs.com;
Hi!
On Tue, Jul 24, 2018 at 10:57:56AM +0200, 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_
(Back online after some weeks away + catching up on
the email backlog)
> On 28 Jun 2018, at 05:01, Jeff Law wrote:
>>* gcc.c (getenv_spec_function): Prepend '/' to value for allowed
>>undefined variables.
>>
> OK
Thanks for this review and the couple of others
in the close timef
On Tue, Jul 31, 2018 at 12:35 AM Alexandre Oliva wrote:
>
> On Jul 24, 2018, Alexandre Oliva wrote:
>
> > Ok to install the first two patches? (the third is just for reference)
>
> Ping?
>
> https://gcc.gnu.org/ml/gcc-patches/2018-07/msg01419.html
OK for the middle-end parts, the Ada parts need
On Mon, Jul 30, 2018 at 7:47 PM Richard Sandiford
wrote:
>
> [Sorry, somehow missed this till now]
>
> Richard Biener writes:
> > On Mon, Jul 23, 2018 at 5:05 PM Richard Sandiford
> > wrote:
> >>
> >> Marc Glisse writes:
> >> > On Fri, 20 Jul 2018, Richard Sandiford wrote:
> >> >
> >> >> --- gc
Hi Tamar,
On 23/07/18 17:52, Tamar Christina wrote:
Hi All,
About 13 years ago the reg-to-reg patterns were split up, before that time
output_move_double could actually handle this case.
After the split was done most patterns were updated except for *neon_mov
which incorrectly retained reg,reg
On Tue, Jul 31, 2018 at 09:02:56AM +0100, Kyrill Tkachov wrote:
> Hi Segher,
>
> On 30/07/18 18:37, Segher Boessenkool wrote:
> >On Mon, Jul 30, 2018 at 03:55:30PM +0100, Kyrill Tkachov wrote:
> >>Hi Segher,
> >>
> >>On 30/07/18 14:14, Segher Boessenkool wrote:
> >>>In arm_block_set_aligned_vect 8
>>> Ok to install the first two patches? (the third is just for reference)
>>
>> Ping?
>>
>> https://gcc.gnu.org/ml/gcc-patches/2018-07/msg01419.html
>
> OK for the middle-end parts, the Ada parts need separate approval
> (maybe CC a maintainer).
Ok for the Ada part.
Arno
On Mon 9 Apr, 2018, 2:06 PM Sameera Deshpande,
wrote:
> Hi Richard,
>
> I do not see the said patch applied in ToT yet. When do you expect it
> to be available in ToT?
>
> - Thanks and regards,
> Sameera D.
>
> On 30 March 2018 at 17:01, Sameera Deshpande
> wrote:
> > Hi Richard,
> >
> > The t
On 31/07/18 12:38, Segher Boessenkool wrote:
On Tue, Jul 31, 2018 at 09:02:56AM +0100, Kyrill Tkachov wrote:
Hi Segher,
On 30/07/18 18:37, Segher Boessenkool wrote:
On Mon, Jul 30, 2018 at 03:55:30PM +0100, Kyrill Tkachov wrote:
Hi Segher,
On 30/07/18 14:14, Segher Boessenkool wrote:
In a
On Tue, Jul 24, 2018 at 12:09 PM Richard Sandiford
wrote:
>
> This patch adds a new helper function for permanently removing a
> statement and its associated stmt_vec_info.
OK.
>
> 2018-07-24 Richard Sandiford
>
> gcc/
> * tree-vectorizer.h (vec_info::remove_stmt): Declare.
>
On Tue, Jul 24, 2018 at 12:09 PM Richard Sandiford
wrote:
>
> This patch adds a helper for replacing a stmt_vec_info's statement with
> a new statement.
OK.
>
> 2018-07-24 Richard Sandiford
>
> gcc/
> * tree-vectorizer.h (vec_info::replace_stmt): Declare.
> * tree-vectorizer.c
On Tue, Jul 24, 2018 at 12:10 PM Richard Sandiford
wrote:
>
> This patch makes free_stmt_vec_info take the stmt_vec_info that
> it's supposed to free and makes it free only that stmt_vec_info.
> Callers need to update the statement mapping where necessary
> (but now there are only a couple of call
On Tue, Jul 24, 2018 at 12:10 PM Richard Sandiford
wrote:
>
> There are no more direct uses of:
>
> - new_stmt_vec_info
> - set_vinfo_for_stmt
> - free_stmt_vec_infos
> - free_stmt_vec_info
>
> outside of vec_info, so they can now be private member functions.
> It also seemed better to put them in
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 vect
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 Sand
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 x86_
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 BT_DERIVED
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,
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 2018-06-
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 char
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 combination
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 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 happe
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 copi
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 implemente
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.
> * dumpf
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 dump_
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 t
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 also
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 im
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 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 implem
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 &s) { this->p = s.p; }
>>
>> private
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 upda
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 in
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, 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 m
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 -m6
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, 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 form
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 usi
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 ac_cv_lib_z_compre
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 dum
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
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 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
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 is
* 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 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 the
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. Fi
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
>
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 for
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 check
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
[PAT
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
IBM
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 Garz
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 distribution
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 uni
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 (select_block_
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
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 dum
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
> an
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
wi
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 _
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
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 ext
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. Go
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 __builtin_goacc
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.
Qu
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 a
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 cu
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 t
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 standard
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
clone_function
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 t
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 (experiment
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 po
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 0
1 - 100 of 137 matches
Mail list logo
