On Thu, Jul 04, 2019 at 01:32:59PM +0100, Jozef Lawrynowicz wrote:
> The attached patch allows the case of register names used in an asm statement
> clobber list to be disregarded when checking the validity of the register
> names.
>
> Currently, the register name used in asm statement clobber
On 07/04/2019 03:43 AM, Richard Biener wrote:
On Thu, Jul 4, 2019 at 2:36 AM Indu Bhagat wrote:
[...]
RE subset of C : It is true that CTF format currently does leave out a very
small subset of C like FIXED_POINT as you noted ( CTF does have representation
for COMPLEX_TYPE, if my code paths
On Wed, 3 Jul 2019, Richard Biener wrote:
On July 3, 2019 4:53:30 PM GMT+02:00, "Martin Liška" wrote:
On 7/2/19 7:15 PM, Marc Glisse wrote:
On Tue, 2 Jul 2019, Martin Liška wrote:
After the discussion with Richi and Nathan, I made a place in
tree_function_decl
and I rebased the original
Hi!
This fixes an ICE in the gimplifier, for VLAs we really can't call
omp_add_variable with GOVD_PRIVATE before the DECL_EXPR is actually
gimplified.
Furthermore, there is really no hope in actually vectorizing such loops and
when we make it just GOVD_LOCAL, we shouldn't mark the loop as
Hi,
> diff --git a/gcc/config/msp430/msp430.c b/gcc/config/msp430/msp430.c
> index 365e9eb..8266fa0 100644
> --- a/gcc/config/msp430/msp430.c
> +++ b/gcc/config/msp430/msp430.c
> @@ -1807,7 +1807,6 @@ const char * const ATTR_CRIT = "critical";
> const char * const ATTR_LOWER = "lower";
>
Hi!
This patch fixes worksharing loops containing both conditional lastprivate
and inscan reduction(s). Furthermore, it for nowait omp for ensures there
is GOMP_loop_end_nowait call at the end after the second loop in scan
and not after the first one.
Bootstrapped/regtested on x86_64-linux and
Hello, gentle maintainer.
This is a message from the Translation Project robot.
A revised PO file for textual domain 'gcc' has been submitted
by the Ukrainian team of translators. The file is available at:
https://translationproject.org/latest/gcc/uk.po
(This file, 'gcc-9.1.0.uk.po', has
Andrea Corallo writes:
> David Malcolm writes:
>
>>> Hi David,
>>> I can work on to get the SVN commit access.
>>> As a maintainer has to sponsor it would you mind being the one?
>>
>> https://www.gnu.org/software/gcc/svnwrite.html says:
>> "a well-established GCC maintainer (including
Hi,
while working on subsetquent changes I noticed that I got worng
the boundary condition while we collect refs.
We know that match1 and match2 are the same which means that we want
to start disambiguating until the last ref that reach the match.
For example when one is MEM_REF and other
Never mind, if the target has reg+offset addressing, the add should be
tried in preference to post_modify, since this enables
reload_combine_recognize_const_pattern .
> Hi.
>
> The patch makes a loop upper bound estimation based on
> __builtin_expect_with_probability.
>
> Patch can bootstrap on x86_64-linux-gnu and survives regression tests.
>
> The patch is pre-approved by Honza.
> Thanks,
> Martin
>
> gcc/ChangeLog:
>
> 2019-07-04 Martin Liska
>
>
Remove the XFAIL on arm in cunroll-15.c since the test passes on trunk.
Committed as obvious.
ChangeLog:
2019-07-04 Wilco Dijkstra
testsuite/
* gcc.dg/tree-ssa/cunroll-15.c: Remove XFAIL on arm.
--
diff --git a/gcc/testsuite/gcc.dg/tree-ssa/cunroll-15.c
Hi.
The patch makes a loop upper bound estimation based on
__builtin_expect_with_probability.
Patch can bootstrap on x86_64-linux-gnu and survives regression tests.
The patch is pre-approved by Honza.
Thanks,
Martin
gcc/ChangeLog:
2019-07-04 Martin Liska
* tree-ssa-loop-niter.c
Andrea Corallo writes:
> Hi Dave,
> last version for this patch addressing the suggestion about the
> JIT_BIT_FIELD macros comment description.
>
> Thank you for all the suggestions.
>
> Regarding the write access please see my previous answer into the binary
> op patch thread.
>
> Bests
>
On 7/4/19 5:03 PM, David Edelsohn wrote:
> On Thu, Jul 4, 2019 at 10:38 AM Martin Liška wrote:
>>
>> Hi.
>>
>> Recently I've introduced a new .gnu.lto_.lto section that
>> is supposed to provide meta information about a LTO bytecode.
>>
>> As a further step, I'm planning to teach binutils about
On Thu, 4 Jul 2019 17:27:28 +0200
Christophe Lyon wrote:
> Finally, I tested on arm-eabi, but not on msp430 for which I do not
> have the environment, so advice from msp430 maintainers is
> appreciated. Since msp430 does not use the same default helpers as
> arm, I left the "noinit" handling
Hi,
Similar to what already exists for TI msp430 or in TI compilers for
arm, this patch adds support for the "noinit" attribute.
It is convenient for embedded targets where the user wants to keep the
value of some data when the program is restarted: such variables are
not zero-initialized. It is
On Thu, Jul 4, 2019 at 10:38 AM Martin Liška wrote:
>
> Hi.
>
> Recently I've introduced a new .gnu.lto_.lto section that
> is supposed to provide meta information about a LTO bytecode.
>
> As a further step, I'm planning to teach binutils about
> existence of the section and I'll remove in the
Hi.
Recently I've introduced a new .gnu.lto_.lto section that
is supposed to provide meta information about a LTO bytecode.
As a further step, I'm planning to teach binutils about
existence of the section and I'll remove in the future
emission of __gnu_lto_slim and __gnu_lto_v1 symbols.
The
This patch has now been backported to openacc-gcc-9-branch (git).
Andre
On 01/07/2019 12:16, Andrew Stubbs wrote:
Improve OpenMP map diagnostics.
2019-07-01 Andrew Stubbs
gcc/cp/
* cp-tree.h (cp_omp_emit_unmappable_type_notes): New prototype.
* decl.c
> checked in. Ok for the gcc-9 branch as well?
Yes.
On 04.07.19 08:50, Arnaud Charlet wrote:
> OK, thanks.
checked in. Ok for the gcc-9 branch as well?
Matthias
>> From: James Clarke
>>
>> Monotonic_Clock and RT_Resolution in the recently-added s-tpopmo.adb
>> call clock_gettime/clock_getres with the integral constants from OSC and
>> thus rely
Hi,
On 27/06/19 23:19, Jason Merrill wrote:
Ah, thanks. Then perhaps we want to change the CLASSTYPE_FINAL in
build_over_call to resolves_to_fixed_type_p (arg), to also handle the
other reasons we might know the dynamic type of the argument, and
remove the related code from
>
> Why does this only happen in fre3?!
After fre1 we have
test (int i, int j, int k, int l)
{
struct c * cptr.0_1;
struct c * cptr2.1_2;
int _11;
:
cptr.0_1 = cptr;
cptr.0_1->b[i_5(D)].a[j_6(D)].val = 123;
cptr2.1_2 = cptr2;
cptr2.1_2->b[k_8(D)].a2[l_9(D)].val = 2;
_11 =
> I don't have commit access so could you please do so on my behalf?
No, I won't be able to do that unfortunately.
By the way do you have a copyright assignment in place?
Arno
The attached patch allows the case of register names used in an asm statement
clobber list to be disregarded when checking the validity of the register names.
Currently, the register name used in asm statement clobber list must exactly
match those defined in the targets REGISTER_NAMES macro.
> On Tue, 25 Jun 2019, Richard Biener wrote:
>
> >
> > PR90911 reports a slowdown of 456.hmmer with the recent introduction
> > of vectorizer versioning of outer loops, more specifically the case
> > of re-using if-conversion created versions.
> >
> > The patch below fixes things up to adjust
>
> The following avoids GC collecting during pass execution when a pass
> calls cgraph::get_body.
>
> Bootstrapped / tested on x86_64-unknown-linux-gnu.
>
> OK?
>
> Thanks,
> Richard.
>
> 2019-07-03 Richard Biener
>
> PR ipa/91062
> * tree-pass.h (execute_all_ipa_transforms):
On 03/07/2019 18:58, Jason Merrill wrote:
OK, thanks.
Committed.
Thanks for the reviews.
Andrew
I don't have commit access so could you please do so on my behalf?
This bug applies to the 9 branch too, so please consider backporting it.
Thanks,
James
> On 4 Jul 2019, at 07:50, Arnaud Charlet wrote:
>
> OK, thanks.
>
>> From: James Clarke
>>
>> Monotonic_Clock and RT_Resolution in the
> Am 03.07.2019 um 22:47 schrieb Richard Sandiford :
>
> Segher Boessenkool writes:
>> On Tue, Jul 02, 2019 at 03:55:56PM +0200, Ilya Leoshkevich wrote:
Am 02.07.2019 um 15:39 schrieb Jakub Jelinek :
On Tue, Jul 02, 2019 at 03:33:28PM +0200, Ilya Leoshkevich wrote:
>> Am 02.07.2019
On Thu, Jul 4, 2019 at 9:01 AM Martin Liška wrote:
>
> Hi.
>
> The patch fixes wrong assignment from a char * to lto_section_header
> that is seen on strict alignment targets.
>
> I verified it fixes the problem with -fsanitize=undefined:
>
> gcc main.o -flto
> ../../gcc/lto/lto-common.c:2202:36:
On Thu, Jul 4, 2019 at 10:29 AM Alexandre Oliva wrote:
>
> On Jul 2, 2019, Richard Biener wrote:
>
> > Yeah, it's on trunk. The parser is ontop of the C frontend and resides
> > in gcc/c/gimple-parser.c while testcases are in gcc.dg/gimplefe-*.c
>
> > The parsing is incomplete, there's no
On Thu, Jul 4, 2019 at 10:19 AM Alexandre Oliva wrote:
>
> On Jul 1, 2019, Richard Biener wrote:
>
> > On Fri, Jun 28, 2019 at 5:21 AM Alexandre Oliva wrote:
> >>
> >> On Jun 27, 2019, Richard Biener wrote:
> >>
> >> > On Thu, Jun 27, 2019 at 10:18 AM Alexandre Oliva
> >> > wrote:
> >>
> >>
On Thu, Jul 4, 2019 at 2:36 AM Indu Bhagat wrote:
>
>
> On 07/03/2019 05:31 AM, Richard Biener wrote:
> > On Wed, Jul 3, 2019 at 5:18 AM Jeff Law wrote:
> >> On 7/2/19 11:54 AM, Indu Bhagat wrote:
> >>> Ping.
> >>> Can someone please review these patches ? We would like to get the
> >>> support
On Thu, 4 Jul 2019 at 12:29, Jakub Jelinek wrote:
>
> On Thu, Jul 04, 2019 at 12:28:12PM +0200, Christophe Lyon wrote:
> > This patch leads to new failures on arm:
> > FAIL: c-c++-common/gomp/scan-3.c (internal compiler error)
> > FAIL: c-c++-common/gomp/scan-5.c (internal compiler error)
>
>
On Wed, Jul 3, 2019 at 2:17 PM Aldy Hernandez wrote:
>
> On 7/3/19 7:08 AM, Richard Biener wrote:
> > On Wed, Jul 3, 2019 at 11:19 AM Aldy Hernandez wrote:
> >>
> >>
> >>
> >> On 7/3/19 4:28 AM, Richard Biener wrote:
> >>> On Mon, Jul 1, 2019 at 10:52 AM Aldy Hernandez wrote:
>
> As
On Thu, Jul 04, 2019 at 12:28:12PM +0200, Christophe Lyon wrote:
> This patch leads to new failures on arm:
> FAIL: c-c++-common/gomp/scan-3.c (internal compiler error)
> FAIL: c-c++-common/gomp/scan-5.c (internal compiler error)
PR91074, already fixed?
Jakub
On Wed, 3 Jul 2019 at 07:11, Jakub Jelinek wrote:
>
> Hi!
>
> The following patch implements roughly the
> https://gcc.gnu.org/ml/gcc-patches/2019-06/msg01330.html
> design for worksharing loops (so far not for composite for simd, that will
> be the next larger task).
>
> Bootstrapped/regtested
Hi Martin,
> The patch fixes wrong assignment from a char * to lto_section_header
> that is seen on strict alignment targets.
>
> I verified it fixes the problem with -fsanitize=undefined:
>
> gcc main.o -flto
> ../../gcc/lto/lto-common.c:2202:36: runtime error: reference binding to
> misaligned
I'm sending one more patch that I've tested.
Martin
>From 44e3202c0416fcaa5a145c32118f0d08ff8ea0a2 Mon Sep 17 00:00:00 2001
From: marxin
Date: Wed, 3 Jul 2019 08:31:35 +
Subject: [PATCH] Backport r272992
gcc/ChangeLog:
2019-07-03 Martin Liska
PR middle-end/90899
* multiple_target.c
Hi.
There are 2 more patches that I've just tested.
Martin
>From ae7d66dad2e43e18cf2889803e30e57bc00f88ad Mon Sep 17 00:00:00 2001
From: marxin
Date: Wed, 3 Jul 2019 08:32:25 +
Subject: [PATCH 2/2] Backport r272993
gcc/ChangeLog:
2019-07-03 Martin Liska
PR tree-optimization/90892
*
The frontend reports spurious errors on C++ non-default constructors
that have formals whose type is an access to subprogram.
Tested on x86_64-pc-linux-gnu, committed on trunk
2019-07-04 Javier Miranda
gcc/ada/
* exp_tss.adb (Init_Proc): Adding missing support for access to
The rule on SPARK_Mode have been modified so that it is now possible to
have a subprogram or package declared with SPARK_Mode Off inside a
subprogram.
Tested on x86_64-pc-linux-gnu, committed on trunk
2019-07-04 Yannick Moy
gcc/ada/
* sem_prag.adb (Check_Library_Level_Entity):
This patch fixes an issue whereby the use of an allocator with a
composite type containing null-excluding components may lead to a
compile time error due to incorrect code generation.
Tested on x86_64-pc-linux-gnu, committed on trunk
2019-07-04 Justin Squirek
gcc/ada/
* exp_ch3.adb
The compiler prematurely freezes a private type that is the type of a
formal parameter of an expression function declared within a nested,
inactivated Ghost package, resulting is an error complaining that the
private type must be fully defined at that point. This is fixed by
testing for
This patch fixes an issue whereby a check for competing controlling
formals led to a spurious dispatching error due to an incomplete type
being used within a subprogram specification.
Tested on x86_64-pc-linux-gnu, committed on trunk
2019-07-04 Justin Squirek
gcc/ada/
* sem_disp.adb
This patch fixes an omission in the construction of equality routines
for variant records, to take into account user-defined equality
functions for components of the record. Previously the constructed
equality routine for variant records used the predefined equality for
all components, When
This patch fixes a spurious error on an attribute reference within an
aspect specification for an unconstrained array type when the
corresponding type declaration appears within a generic unit.
Tested on x86_64-pc-linux-gnu, committed on trunk
2019-07-04 Ed Schonberg
gcc/ada/
*
This patch fixes an issue whereby instantiation of a generic at the
library-level may cause a hang or crash during compilation due to
inappropriate expansion of generic actuals.
Tested on x86_64-pc-linux-gnu, committed on trunk
2019-07-04 Justin Squirek
gcc/ada/
* sem_ch12.adb
This removes old code in the parser that serves no useful purpose and
fixes minor issues in the Validsw package. No functional changes.
Tested on x86_64-pc-linux-gnu, committed on trunk
2019-07-04 Eric Botcazou
gcc/ada/
* gnat1drv.adb (Adjust_Global_Switches): Use proper interface
The definition of what types yield synchronized objected in SPARK has
been updated to see through the privacy boundary.
Tested on x86_64-pc-linux-gnu, committed on trunk
2019-07-04 Yannick Moy
gcc/ada/
* sem_util.adb (Yields_Synchronized_Object): Adapt to new SPARK
rule.
This patch fixes a spurious error during the construction of an instance
body in the inlining phase of the frontend, when the package declaration
for the main unit has a limited_with_clause on some unit P, and the main
unit itself does not have a corresponding regular with_clause, but some
other
This patch modifies the timing of Sem_Elab's internal data structure
creation and destruction, and adds the concept of "active" elaboration
compiler phase.
The elaboration phase of the compiler is active after the frontend
initializes Sem_Elab. It is at this point that all internal data
When SPARK code does not follow the ownership rules of SPARK RM 3.10,
the error message now points to a location explaining why the object has
a more restricted permission than the expected one.
There is no impact on compilation.
Tested on x86_64-pc-linux-gnu, committed on trunk
2019-07-04
This patch prevents the association of a Default_Initial_Condition with
an incomplete type whose full view is the private type or private
extension subject to the aspect/pragma.
Tested on x86_64-pc-linux-gnu, committed on trunk
2019-07-04 Hristian Kirtchev
gcc/ada/
* sem_util.adb
This patch fixes a spurious dimensionality error on an array aggregate
with a single "others' clause whose expression is a dimensioned entity,
The expansion of the aggregate may create copies of the expression, and
the dimensionality check must use the type of the expression to retrieve
the proper
Analysis could crash on extended return of a non-deep type, now fixed.
This has no impact on compilation.
Tested on x86_64-pc-linux-gnu, committed on trunk
2019-07-04 Yannick Moy
gcc/ada/
* sem_spark.adb (Check_Statement): Only check permission of
object in extended return
In GNATprove mode the assertion policy is now always enabled, even when
analysing internal units. Otherwise, assertion expressions (e.g.
Default_Initial_Condition) in internal units (e.g. Ada.Text_IO)
disappear in the semantic analysis phase of the frontend and the
GNATprove backend can't see
Ownership rules for pointer support should only apply to code marked in
SPARK. There is no impact on compilation.
Tested on x86_64-pc-linux-gnu, committed on trunk
2019-07-04 Yannick Moy
gcc/ada/
* sem_spark.adb (Check_Package_Spec, Check_Package_Body): Only
analyze parts of
On Jul 2, 2019, Richard Biener wrote:
> Yeah, it's on trunk. The parser is ontop of the C frontend and resides
> in gcc/c/gimple-parser.c while testcases are in gcc.dg/gimplefe-*.c
> The parsing is incomplete, there's no support for parsing try/catch/finally
I'm afraid I haven't got very
On 2017/10/31 8:17 AM, Joseph Myers wrote:
Specifically,*non-release* versions of binutils predating my patch
commit 066c2a57f5858310c9f12518317aecd4b54e753d
Author: Joseph Myers
Date: Thu Mar 1 15:48:36 2007 +
would have had a space between the binutils version number and the BFD
See below for modified patch, indentation and newline for curly braces
style applied, and commented out chunk removed. Apologies, indentation
and newline for scope are not they way I normally write things, habits
got the better of me, and I forgot to remove the commented out chunk
before
On Jul 1, 2019, Richard Biener wrote:
> On Fri, Jun 28, 2019 at 5:21 AM Alexandre Oliva wrote:
>>
>> On Jun 27, 2019, Richard Biener wrote:
>>
>> > On Thu, Jun 27, 2019 at 10:18 AM Alexandre Oliva wrote:
>>
>> >> @@ -909,6 +909,13 @@ DEFTREECODE (TRY_CATCH_EXPR, "try_catch_expr",
>> >>
I'm working on a patch that needs to keep track of more state
during the walk_non_aliased_vuses walks in VN. This refactors
the existing code to avoid using global variables, introducing
a state structure that I will extend later.
Bootstrapped / tested on x86_64-unknown-linux-gnu, applied.
On Thu, 4 Jul 2019, Jakub Jelinek wrote:
> On Wed, Jul 03, 2019 at 12:49:34PM +0200, Richard Biener wrote:
> > 2019-07-03 Richard Biener
> >
> > PR middle-end/91069
> > * match.pd (vec_perm -> bit_insert): Fix element read from
> > first vector.
> >
> > * gcc.dg/pr91069.c:
On Thu, 4 Jul 2019, Jakub Jelinek wrote:
> Hi!
>
> A recent change in vect_init_vector emits new statements into a gimple_seq
> stmts and then calls vect_init_vector_1 on each of those statements.
>
> This doesn't work well, because vect_init_vector_1 places the given
> statement into another
Hi.
The patch fixes wrong assignment from a char * to lto_section_header
that is seen on strict alignment targets.
I verified it fixes the problem with -fsanitize=undefined:
gcc main.o -flto
../../gcc/lto/lto-common.c:2202:36: runtime error: reference binding to
misaligned address
OK, thanks.
> From: James Clarke
>
> Monotonic_Clock and RT_Resolution in the recently-added s-tpopmo.adb
> call clock_gettime/clock_getres with the integral constants from OSC and
> thus rely on clockid_t being an integral type, so we cannot hide it on
> GNU/kFreeBSD. Instead, make the
On Wed, 3 Jul 2019 at 17:06, Richard Sandiford
wrote:
>
> Prathamesh Kulkarni writes:
> > On Tue, 2 Jul 2019 at 18:22, Richard Sandiford
> > wrote:
> >>
> >> Prathamesh Kulkarni writes:
> >> > On Tue, 2 Jul 2019 at 16:59, Richard Sandiford
> >> > wrote:
> >> >>
> >> >> Thanks for fixing this.
70 matches
Mail list logo
