On 06/19/2018 02:10 PM, Martin Sebor wrote:
> On 06/19/2018 01:33 PM, David Edelsohn wrote:
>> Martin,
>>
>> Does attr-nonstring-3.c assume a 64 bit environment?
>
> I don't think so. The error below suggests a problem during
> the expansion of the strncmp built-in. The patch didn't
> change tha
HXT semiconductor's CPU core Phecda, as a variant of Qualcomm qdf24xx,
reuses the same tuning structure and pipeline with it.
2018-06-19 Hongbo Zhang
* config/aarch64/aarch64-cores.def (AARCH64_CORE): add phecda core
* config/aarch64/aarch64-tune.md: re-generated by gentune.sh
On Tue, 19 Jun 2018, Segher Boessenkool wrote:
> > Because the names depend on the format not the type, there is no risk of
> > ABI inconsistency from linking with a libgcc function for the wrong
> > format, and so I think the linker warning is never relevant for linking
> > with libgcc (and on
On Tue, 19 Jun 2018, co...@sdf.org wrote:
> Hi! I have no commit access.
> Can someone commit it?
I'll take care.
Gerald
Hi!
On Tue, Jun 19, 2018 at 01:37:51PM -0500, Kelvin Nilsen wrote:
> --- gcc/testsuite/gcc.target/powerpc/builtins-9.c (nonexistent)
> +++ gcc/testsuite/gcc.target/powerpc/builtins-9.c (working copy)
> @@ -0,0 +1,21 @@
> +/* { dg-do compile } */
> +/* { dg-require-effective-target powerpc_
Hi,
the Ada compiler uses small functions defined in its runtime to implement
various intrinsic operations and it always inlines them, even at -O0. But it
doesn't want location information from the runtime files to appear in the
debug info so it puts DECL_IGNORED_P on these functions. final.c
On Tue, Jun 19, 2018 at 03:31:55PM +, Joseph Myers wrote:
> On Sun, 4 Feb 2018, Maya Rashish wrote:
>
> > Of the currently supported BSDs:
> > - FreeBSD, doesn't have ansi.h or define _MACHINE_ANSI_H anywhere
> > in its other headers since the long-gone 5.x release.
> > - OpenBSD, DragonflyBSD
Hi Carl,
On Mon, Jun 18, 2018 at 01:52:15PM -0700, Carl Love wrote:
> Per our discussions, the previous patch had issues with the target
> !powerpc*-*-aix* not working correctly and thus the instruction count
> test was not being done. I have addressed those issues and verified by
> inspecting th
On Mon, Jun 18, 2018 at 04:38:44AM -0500, Andre Simoes Dias Vieira wrote:
> Hi,
>
> This patch teaches the AArch64 backend that AES instructions with a XOR and
> zero operands can be simplified by replacing the operands of the AES with
> XOR's thus eliminating the XOR. This is OK because the AES i
On Mon, Jun 18, 2018 at 04:38:27AM -0500, Andre Simoes Dias Vieira wrote:
> Hi,
>
> This patch teaches the AArch64 backend that the AESE and AESD unspecs are
> commutative (which correspond to the vaeseq_u8 and vaesdq_u8 intrinsics).
> This improves register allocation around their corresponding i
As explained in the audit trail, the goal of the fix for PR debug/44205:
* tree-cfgcleanup.c (tree_forwarder_block_p): Return false if
at -O0 goto_locus of any of the incoming edges differs from
goto_locus of outgoing edge, or gimple_location of any of the
labels differ
On Mon, Jun 18, 2018 at 03:34:37PM -0400, Michael Meissner wrote:
> This is just the combined patch of the last three patches that have been
> approved for trunk. I expanded the description in rs6000-modes.def of what
> the
> 3 128-bit floating point types are and why IFmode needs to be ordered a
On Tue, Jun 19, 2018 at 09:09:27AM -0500, Tamar Christina wrote:
> Hi All,
>
> This changes the movmem code in AArch64 that does copy for data between 4 and
> 7
> bytes to use the smallest possible mode capable of copying the remaining
> bytes.
>
> This means that if we're copying 5 bytes we wo
On Fri, Jun 15, 2018 at 08:43:52PM +, Joseph Myers wrote:
> On Thu, 14 Jun 2018, Michael Meissner wrote:
>
> > Any other libgcc function that has a long double interface should get the
> > linker warning that the wrong type was used.
>
> libgcc functions have interfaces corresponding to a par
Hi,
the below implements a couple of independent ideas. First, adds a const
cp_decl_specifier_seq * parameter, similarly to grokvardecl: this way
the function has available locations[ds_inline],
locations[ds_constexpr], locations[ds_type_spec] which can use in some
error messages. Second, the
On Mon, Jun 18, 2018 at 03:06:18PM -0400, Michael Meissner wrote:
> On Fri, Jun 15, 2018 at 04:00:42PM -0500, Segher Boessenkool wrote:
> > But those aren't types, those are modes. Why would the modes not work?
> > That makes no sense. Just like the __ieee128 and __ibm128 types work
> > always, s
On 06/19/2018 02:10 PM, Martin Sebor wrote:
On 06/19/2018 01:33 PM, David Edelsohn wrote:
Martin,
Does attr-nonstring-3.c assume a 64 bit environment?
I don't think so. The error below suggests a problem during
the expansion of the strncmp built-in. The patch didn't
change that. I see GCC
> On testcases like that from PR60243 CFG build is dominated by
> assign_discriminators because it expands locations again and again
> and this got more expensive over the time.
>
> Cary - can you explain the overall logic of assign_discriminators,
> specifically why if the last stmt of a block has
On 06/19/2018 01:33 PM, David Edelsohn wrote:
Martin,
Does attr-nonstring-3.c assume a 64 bit environment?
I don't think so. The error below suggests a problem during
the expansion of the strncmp built-in. The patch didn't
change that. I see GCC 8 ICE on the test as well so it must
be a lat
Martin,
Does attr-nonstring-3.c assume a 64 bit environment?
I'm seeing new errors on the rs6000 port
FAIL: gcc.dg/attr-nonstring-3.c (internal compiler error)
/nasfarm/edelsohn/src/src/gcc/testsuite/gcc.dg/attr-nonstring-3.c:73:1:
error: could not split insn
(insn 3244 3245 3246 (set (reg:SI 5
Hi!
On Mon, Jun 18, 2018 at 11:29:55AM -0500, Kelvin Nilsen wrote:
> +/* A single vpkudus matches twice because this is compiled with -dp,
> + causing diagnostic comments to appear in the resulting .s file, one
> + of which matches vpkudus. */
-dp prints the name of the instruction pattern,
I hadn't previously been aware of this flag, and so introduced
CONSTRUCTOR_NO_IMPLICIT_ZERO in the C++ front end. Better to use the
language-independent flag, since there is one.
Tested x86_64-pc-linux-gnu, applying to trunk.
commit b10a3fd2862b614227de5a94332ebc43a752f727
Author: Jason Merrill
On 06/19/2018 12:46 PM, Jason Merrill wrote:
On Tue, Jun 19, 2018 at 2:44 PM, Jason Merrill wrote:
On Tue, May 29, 2018 at 3:21 PM, Martin Sebor wrote:
To make review and testing easier (thank you, Franz), attached
is an updated patch rebased on top of today's trunk.
(Note that the patch int
On Tue, May 29, 2018 at 3:21 PM, Martin Sebor wrote:
> To make review and testing easier (thank you, Franz), attached
> is an updated patch rebased on top of today's trunk.
>
> (Note that the patch intentionally doesn't suppress the warning
> for the submitted test case without adding the nonstrin
On Tue, Jun 19, 2018 at 2:44 PM, Jason Merrill wrote:
> On Tue, May 29, 2018 at 3:21 PM, Martin Sebor wrote:
>> To make review and testing easier (thank you, Franz), attached
>> is an updated patch rebased on top of today's trunk.
>>
>> (Note that the patch intentionally doesn't suppress the warn
Someone found a sneaky way to use an anonymous union type as a
template argument. That seems to me like it ought to be ill-formed,
but this patch is a simple enough way to make this testcase work.
Tested x86_64-pc-linux-gnu, applying to trunk.
commit 4f51a88ed61f69fd483a46b93f0ba9cff352324a
Autho
This patch fixes an error in the code generation for vec_pack (vector double,
vector double). As previously implemented, this built-in function translates
to the vpkudum instruction.
This patch causes vec_pack (vector double, vector double) to behave the same as
vec_float2 for the same type
On Tue, Jun 19, 2018 at 10:11 AM, augustine.sterl...@gmail.com
wrote:
> On Mon, Jun 18, 2018 at 3:10 PM, Max Filippov wrote:
>>
>> gcc/
>> 2018-06-17 Max Filippov
>>
>> * config/xtensa/xtensa.md (UNSPEC_FRAME_BLOCKAGE): New unspec
>> constant.
>> (allocate_stack, frame_
On Fri, Jun 15, 2018 at 03:56:57PM -0400, Michael Meissner wrote:
> On Fri, Jun 15, 2018 at 01:39:49PM -0500, Segher Boessenkool wrote:
> > On Wed, Jun 13, 2018 at 05:25:33PM -0400, Michael Meissner wrote:
> > > This patch fixes the power8 implementation of copysign for IEEE 128-bit
> > > floating
This header was needed for the declaration of std::terminate but the
calls to it were removed in r242401.
* include/std/utility: Remove unused header.
Tested powerpc64le-linux, committed to trunk, gcc-8 and gcc-7.
commit d56e1f3ab3e633e47cdd0b13cd70d0b1423b876b
Author: Jonathan Wakely
On Mon, Jun 18, 2018 at 3:10 PM, Max Filippov wrote:
> gcc/
> 2018-06-17 Max Filippov
>
> * config/xtensa/xtensa.md (UNSPEC_FRAME_BLOCKAGE): New unspec
> constant.
> (allocate_stack, frame_blockage, *frame_blockage): New patterns.
>
This is OK.
This patch updates the existing OpenACC libgomp runtime tests with the
new OpenACC 2.5 data clause semantics.
Is it OK for trunk?
Cesar
2018-06-19 Chung-Lin Tang
Thomas Schwinge
Cesar Philippidis
libgomp/
* testsuite/libgomp.oacc-c-c++-common/data-already-1.c: Update test
case
This patch updates the existing OpenACC compiler tests with the new
OpenACC 2.5 data clause semantics.
Is it OK for trunk?
Cesar
2018-06-19 Chung-Lin Tang
Thomas Schwinge
Cesar Philippidis
gcc/testsuite/
* c-c++-common/goacc/declare-1.c: Update test case to utilize OpenACC
2.5
This patch implements the OpenACC 2.5 data clause semantics in libgomp.
Is it OK for trunk?
Cesar
2018-06-19 Chung-Lin Tang
Thomas Schwinge
Cesar Philippidis
libgomp/
* libgomp.h (struct splay_tree_key_s): Add dynamic_refcount member.
(gomp_acc_remove_pointer): Update declarati
This patch implements the OpenACC 2.5 data clause semantics in the
middle end.
Is it OK for trunk?
Cesar
2018-06-19 Chung-Lin Tang
Thomas Schwinge
Cesar Philippidis
gcc/c-family/
* c-pragma.h (enum pragma_omp_clause): Add
PRAGMA_OACC_CLAUSE_{FINALIZE,IF_PRESENT}. Remove
PRAGMA
This patch implements the OpenACC 2.5 data clause semantics in the
Fortran FE.
Is it OK for trunk?
Cesar
2018-06-19 Chung-Lin Tang
Thomas Schwinge
Cesar Philippidis
gcc/fortran/
* gfortran.h (gfc_omp_clauses): Add unsigned if_present, finalize
bitfields.
* openmp.c (enum omp_m
This patch implements the OpenACC 2.5 data clause semantics in the C FE.
Is it OK for trunk?
Cesar
2018-06-19 Chung-Lin Tang
Thomas Schwinge
Cesar Philippidis
gcc/c/
* c-parser.c (c_parser_omp_clause_name): Add support for finalize
and if_present. Make present_or_{copy,copyin,c
This patch implements the OpenACC 2.5 data clause semantics in the C++ FE.
Is it OK for trunk?
Cesar
2018-06-19 Chung-Lin Tang
Thomas Schwinge
Cesar Philippidis
gcc/cp/
* parser.c (cp_parser_omp_clause_name): Add support for finalize
and if_present. Make present_or_{copy,copyin
Ping.
To make this patch easier to review, I'll split it into individual
patches for each major component in follow up emails.
Cesar
On 05/25/2018 01:01 PM, Cesar Philippidis wrote:
> This patch updates GCC's to support OpenACC 2.5's data clause semantics.
> In OpenACC 2.5, copy, copyin and cop
Hi Rasmus,
> On 4 Jun 2018, at 16:46, Rasmus Villemoes wrote:
>
> These are some of the patches I'm currently applying to get a full C
> and C++ compiler to work for powerpc-wrs-vxworks (for vxworks
> 5.5). With these, and a few more, I have ZCX, static
> constuctors/destructors and throwing acr
On June 19, 2018 6:05:59 PM GMT+02:00, Richard Sandiford
wrote:
>Richard Biener writes:
>> The following is an (incomplete) attempt at making the vectorizer
>> share dataref and dependence analysis for loop vectorization when
>> analyzing the loop for multiple vector sizes.
>>
>> A prerequesite
Richard Biener writes:
> The following is an (incomplete) attempt at making the vectorizer
> share dataref and dependence analysis for loop vectorization when
> analyzing the loop for multiple vector sizes.
>
> A prerequesite for sharing the datarefs and dependence relations
> is that they are not
On Thu, Jun 07, 2018 at 05:58:01AM -0500, Kyrill Tkachov wrote:
>
> On 05/06/18 18:28, James Greenhalgh wrote:
> > On Tue, Jun 05, 2018 at 11:32:06AM -0500, Kyrill Tkachov wrote:
> >> On 04/06/18 18:40, Kyrill Tkachov wrote:
> >>> Hi all,
> >>>
> >>> This patch adds support for generating LDPs and
On Thu, 7 Jun 2018, Olivier Hainque wrote:
> An updated version of the patch is attached, accounting for
> your two comments and expanding on the .texi documentation a
> bit.
I see you're not changing LINK_GCC_C_SEQUENCE_SPEC in arc/elf.h. That's a
slightly odd case in that it isn't actually u
Hi Tamar,
On 19/06/18 15:07, Tamar Christina wrote:
Hi All,
This fixes a regression where we don't have an instruction for pre Armv8.2-a
to do a move of an fp16 value from a GP reg to a SIMD reg.
This patch adds that pattern to movhf_aarch64 using a dup and only selectes it
using a very low pr
On Mon, Jun 18, 2018 at 08:43:04AM -0500, Siddhesh Poyarekar wrote:
> r217431 changed X30 as caller-saved in CALL_USE_REGISTERS because of
> which this comment about X30 not being marked as call-clobbered is no
> longer accurate.
Is the second paragraph is still relevant to how we define EPILOGUE_
On Sun, 4 Feb 2018, Maya Rashish wrote:
> Of the currently supported BSDs:
> - FreeBSD, doesn't have ansi.h or define _MACHINE_ANSI_H anywhere
> in its other headers since the long-gone 5.x release.
> - OpenBSD, DragonflyBSD don't have ansi.h either.
> - NetBSD, sole remaining with ansi.h
>
> Rep
On Tue, 19 Jun 2018, Steve Ellcey wrote:
> The problem with this is that num_linker_inputs isn't getting
> incremented when it sees a file to be turned into a precompiled header
> it gets incremented when it sees a linker flag like '-rpath'.
>
> The comments in driver::prepare_infiles make it see
This patch fixes spurious failure for C test added with original patch
for bug 55976.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=55976
Added dg-prune-output for extraneous message causing unexpected test
failure for test gcc.dg/noncompile/pr55976-1.c
Bootstrap tests run successfully x86_64
> > Hmm, I do not think we should try to merge -O0 functions :)
> > But again, if you have testcase that triggers this path, we could
> > handle it later.
>
> This is valid:
>
> ./xgcc -B. /home/marxin/Programming/gcc/gcc/testsuite/g++.dg/ipa/pr64146.C
> -fipa-icf
> during IPA pass: icf
> /home/
On Fri, 2018-06-08 at 11:17 +, Joseph Myers wrote:
> On Wed, 2 May 2018, Steve Ellcey wrote:
>
> >
> > I tracked this down to driver::maybe_run_linker where it sees the linker
> > flags and increments num_linker_inputs, this causes the routine to call
> > the linker. This patch checks to se
On 06/19/2018 03:37 PM, Jan Hubicka wrote:
>> Hello.
>>
>> ICEs on:
>>
>> $ cat ice.ii
>> #pragma GCC optimize 0
>> int main() {}
>>
>> $ ./xgcc -B. -O2 ice.ii
>> during IPA pass: cp
>> ice.ii:2:13: internal compiler error: Segmentation fault
>> int main() {}
>> ^
>> 0xdbb6bf crash_si
The following is an (incomplete) attempt at making the vectorizer
share dataref and dependence analysis for loop vectorization when
analyzing the loop for multiple vector sizes.
A prerequesite for sharing the datarefs and dependence relations
is that they are not changed during the analysis phas
Hi All,
This patch requires https://gcc.gnu.org/ml/gcc-patches/2018-06/msg01145.html to
work,
it has been accepted once already but caused a regression on certain
configuratoins.
I am re-submitting it with the required mid-end change and requesting a
back-port.
--- original patch.
Taking the
Hi All,
Previously GCC's no-op detection could would consider something a no-op even
when the
mode change is not directly possible. This caused subregs that shouldn't be
removed
to be treated as a no-op and deleted.
Regtested on armeb-none-eabi and no regressions.
Bootstrapped on arm-none-linu
Hi All,
This changes the movmem code in AArch64 that does copy for data between 4 and 7
bytes to use the smallest possible mode capable of copying the remaining bytes.
This means that if we're copying 5 bytes we would issue an SImode and QImode
load instead of two SImode loads.
This does smaller
Hi All,
This fixes a regression where we don't have an instruction for pre Armv8.2-a
to do a move of an fp16 value from a GP reg to a SIMD reg.
This patch adds that pattern to movhf_aarch64 using a dup and only selectes it
using a very low priority.
This fixes an ICE at -O0.
Regtested on aarch6
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 Spanish team of translators. The file is available at:
http://translationproject.org/latest/gcc/es.po
(This file, 'gcc-8.1.0.es.po', has just
> Hello.
>
> ICEs on:
>
> $ cat ice.ii
> #pragma GCC optimize 0
> int main() {}
>
> $ ./xgcc -B. -O2 ice.ii
> during IPA pass: cp
> ice.ii:2:13: internal compiler error: Segmentation fault
> int main() {}
> ^
> 0xdbb6bf crash_signal
> /home/marxin/Programming/gcc/gcc/toplev.c
Updated patch with a new test.
Use __builtin_memmove for trivially copy assignable types
2018-06-19 Glen Joseph Fernandes
* include/bits/stl_algobase.h
(__is_simple_copy_move): Defined helper.
(__copy_move_a): Used helper.
(__copy_move_backward_a): Likewise.
* testsuite/20
On 06/15/2018 05:05 PM, Jan Hubicka wrote:
>> Hi.
>>
>> This is first part of IPA summary conversion clean-up. It removes
>> ::get_create and
>> uses ::get for ipa-inline related symbol (and call) summaries. I'm planning
>> to
>> investigate also other summaries.
>>
>> Patch can bootstrap on x86_
On 06/12/2018 02:18 PM, Martin Liška wrote:
> Hi.
>
> Following patch improves GIMPLE VIM syntax format. Please take a look
> at attached screenshots.
>
> Ready for trunk?
> Martin
>
> https://drive.google.com/file/d/1KK3GvfX-VXtI_S-TOcIrPq-pex1WTAIJ/view?usp=sharing
> https://drive.google.com/f
On 06/15/2018 06:18 PM, Alexander Monakov wrote:
> On Fri, 15 Jun 2018, Martin Liška wrote:
>> So you prefer to come up with a plugin folder with the *.vim files?
>
> Yes, the main reason being very simple installation if already using a
> plugin manager. A plugin folder may contain a custom ftdet
This refactors the main loop vectorization loop to avoid all the
gotos which stand in the way of me adding a local with a constructor.
On the way I fixed the dbgcnt handling now that we support things
like 2:5 which the vectorizer mishandles by simply aborting the loop
walk.
Bootstrapped and te
The existing code allows only 4 vectors worth of ieee128 homogeneous
aggregates, but it should be 8. This happens because at one spot it
is mistakenly qualified as being passed in floating point registers.
This patch fixes it and makes the code easier to read. Committing to
trunk; needs backport
Richard Biener wrote:
> There are a number of regression tests that check for errno handling
> (I added some to avoid aliasing for example). Please make sure to
> add explicit -fmath-errno to those that do not already have it set
> (I guess such patch would be obvious and independent of this one)
On Mon, Jun 18, 2018 at 4:51 PM Richard Sandiford
wrote:
>
> This patch is the first part of a series to fix to PR85694.
> Later patches can make the pattern for a statement S2 reuse the
> results of a PATTERN_DEF_SEQ statement attached to an earlier
> statement S1. Although vect_mark_stmts_to_be
On Mon, Jun 18, 2018 at 4:53 PM Richard Sandiford
wrote:
>
> A pattern's PATTERN_DEF_SEQ was attached to both the original statement
> and the main pattern statement, which made it harder to update later.
> This patch attaches it to just the original statement. In practice,
> anything that cared
On Mon, Jun 18, 2018 at 5:04 PM Richard Sandiford
wrote:
>
> When following the definitions of SSA names, some recognisers
> already cope with statements that have been replaced by patterns.
> This patch makes that happen automatically for users of
> type_conversion_p and vect_get_internal_def. I
On Mon, Jun 18, 2018 at 5:01 PM Richard Sandiford
wrote:
>
> This patch makes pattern recognisers do their own checking for vector
> types and target support. Previously some recognisers did this
> themselves and some left it to vect_pattern_recog_1.
>
> Doing this means we can get rid of the typ
On Mon, Jun 18, 2018 at 5:00 PM Richard Sandiford
wrote:
>
> This message is a long write-up for a patch that simply adds a common
> routine for printing the "vector_foo_pattern: detected:" messages.
>
> The reason for doing this is that some routines check for target support
> themselves and some
On Mon, Jun 18, 2018 at 4:58 PM Richard Sandiford
wrote:
>
> This patch adds a helper for pattern code that wants to find an
> internal (vectorisable) definition of an SSA name.
>
> A later patch will make more use of this, and alter the definition.
>
> Tested on aarch64-linux-gnu and x86_64-linux
On Mon, Jun 18, 2018 at 4:57 PM Richard Sandiford
wrote:
>
> vect_recog_dot_prod_pattern and vect_recog_sad_pattern both checked
> whether the statement passed in had already been recognised as a
> WIDEN_SUM_EXPR pattern. That isn't possible (any more?), since the
> first recognised pattern wins,
On Mon, Jun 18, 2018 at 4:55 PM Richard Sandiford
wrote:
>
> tree-vect-patterns.c checked that operands to primitive arithmetic ops
> are compatible with each other and with the result. The checks date
> back years and have long been redundant with verify_gimple_stmt.
>
> Tested on aarch64-linux-
On Mon, Jun 18, 2018 at 4:54 PM Richard Sandiford
wrote:
>
> vectorizable_call stubs out the original scalar statement with
> a dummy assignment to the same lhs, so that we don't leave any bogus
> scalar calls around. If the call is actually a pattern statement,
> the code rightly took the lhs of
Hi!
The flush directive can now have optional memory-order clause.
Tested on x86_64-linux, committed to gomp-5_0-branch.
2018-06-19 Jakub Jelinek
c-family/
* c-common.h (c_finish_omp_flush): Add MO argument.
* c-omp.c: Include memmodel.h.
(c_finish_omp_flush): Add MO
On Tue, Jun 19, 2018 at 10:11 AM Eric Botcazou wrote:
>
> Hi,
>
> as spotted by Richard B., there is an oversight in the implementation of
> CONSTRUCTOR_NO_CLEARING in the gimplifier: it may be overruled depending on
> the outcome of the clearing heuristics.
>
> Tested on x86-64/Linux, OK for the
I got caught with a wild goose chase with this one. I tried to get it
to work before seeing the standard reference in trans-expr.c. In fact,
it would be impossible to fix because there is no way to resolve
different instances of the abstract interface with different character
lengths.
Bootstrapped
On Mon, Jun 18, 2018 at 8:35 PM Denis Khalikov
wrote:
>
> Hello,
> this is a patch for PR other/86198
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86198
> Thanks.
OK.
Richard.
Hi.
I'm removing unused 'stagestuff' in config-lang.in. I'm going
to install it as obvious.
Thanks,
Martin
gcc/lto/ChangeLog:
2018-06-19 Martin Liska
* config-lang.in: Remove stagestuff.
---
gcc/lto/config-lang.in | 1 -
1 file changed, 1 deletion(-)
diff --git a/gcc/lto/config-l
Hi Christophe,
On 17/06/18 21:23, Christophe Lyon wrote:
On Fri, 15 Jun 2018 at 17:22, Richard Earnshaw (lists)
wrote:
>
> On 15/06/18 15:30, Christophe Lyon wrote:
> > Hello,
> >
> > As suggested in [1], the attached patch removes all definitions and
> > uses of __ARM_ARCH__ and uses __ARM_ARC
On Mon, Jun 18, 2018 at 4:01 PM Wilco Dijkstra wrote:
>
> GCC currently defaults to -fmath-errno. This generates code assuming math
> functions set errno and the application checks errno. Few applications
> test errno and various systems and math libraries no longer set errno since it
> is optio
Hi,
as spotted by Richard B., there is an oversight in the implementation of
CONSTRUCTOR_NO_CLEARING in the gimplifier: it may be overruled depending on
the outcome of the clearing heuristics.
Tested on x86-64/Linux, OK for the mainline? Can I put this on the 8 and 7
branches too (only the Ad
Richard Biener writes:
> Pattern recognition can leave stale STMT_VINFO_RELATED_STMT entries
> around which confuses the correctness asserting I put into
> get_{earlier,later}_stmt. The following makes sure to clear
> those again. To make things more complicated pattern recognition
> sometimes s
so that gcc builds in a reproducible way
in spite of indeterministic filesystem readdir order
See https://reproducible-builds.org/ for why this is good.
While working on the reproducible builds effort, I found that
when building the gcc8 package for openSUSE, there were differences
between each b
Hi!
#pragma omp taskwait depend(...)
is syntactic sugar for:
#pragma omp task if(0) mergeable depend(...)
;
but we can optimize a little bit and not outline the empty body or
really construct the new task.
Tested on x86_64-linux, committed to gomp-5_0-branch.
2018-06-19 Jakub Jelinek
86 matches
Mail list logo
