[PATCH] MAINTAINERS: Change to my personal email address

I'm leaving SiFive in a bit less than two weeks, which means I'll be losing my @sifive email address. I don't have my new email address yet, so I'm switching over to my personal address instead. 2019-10-29 Palmer Dabbelt * MAINTAINERS: Change pal...@sifive.com to pal...@dabbelt.com.

Re: [C++ Patch] Prefer error + inform in four typeck.c places

On 10/24/19 10:07 AM, Paolo Carlini wrote: Hi, some additional straightforward bits in typeck.c, which I noticed when I went through the cp_build_binary_op callers. Tested x86_64-linux. Thanks, Paolo. // OK.

[PATCH V2] rs6000: Refine unroll factor with target unroll_adjust hook.

Hi, In this patch, loop unroll adjust hook is introduced for powerpc. In this hook, we can do target related hueristic adjustment. For this patch, we tunned for O2 to unroll small loops with small unroll factor (2 times), for other optimization, default unroll factor is used. Bootstrapped and

Re: [PATCH] rs6000: Refine implicit funroll-loops with unroll_adjust hook.

Richard Biener writes: > On Tue, 29 Oct 2019, Jiufu Guo wrote: > >> For this patch at -flto, loop-unrolling is affected by command line >> besides optimize level per function. >> -flto -c t.c -O2 -funroll-loops >> -flto t.o -O2 or -flto t.o, >> this linking will not be treated as explicit

Re: [RFC PATCH] targetm.omp.device_kind_arch_isa and OpenMP declare variant kind/arch/isa handling

On Tue, Oct 29, 2019 at 05:40:11PM -0500, Segher Boessenkool wrote: > On Tue, Oct 29, 2019 at 06:15:31PM +0100, Jakub Jelinek wrote: > > The standard makes it implementation defined what an arch is and what is > > isa, but I think because there is no selector like target that arch should > >

Re: [RFC PATCH] targetm.omp.device_kind_arch_isa and OpenMP declare variant kind/arch/isa handling

Hi! On Tue, Oct 29, 2019 at 06:15:31PM +0100, Jakub Jelinek wrote: > The standard makes it implementation defined what an arch is and what is > isa, but I think because there is no selector like target that arch should > mostly contain identifiers that match the ABI incompatible stuff (target, >

Re: [PATCH 2/2] Remove cgraph_local_info structure.

On 10/25/19 7:38 AM, Martin Liska wrote: > > gcc/ChangeLog: > > 2019-10-25 Martin Liska > > * cgraph.c (cgraph_node::local_info): Transform to ... > (cgraph_node::local_info_node): ... this. > (cgraph_node::dump): Remove cgraph_local_info and > put its fields directly

Re: C++ PATCH for c++/90998 - ICE with copy elision in init by ctor and -Wconversion

On 10/25/19 2:38 PM, Marek Polacek wrote: After r269667 which introduced joust_maybe_elide_copy, in C++17 we can elide a constructor if it uses a conversion function that returns a prvalue, and use the conversion function in its stead. This eliding means that if we have a candidate that

Re: [C++ PATCH] Fix a C++17/20 regression on indirect function calls (PR c++/92201)

On 10/23/19 6:35 PM, Jakub Jelinek wrote: Hi! For middle-end pointer conversions are useless, which means the gimplifier can change the type of the value being gimplified. gimplify_call_expr is careful about this and remembers the fnptrtype early before gimplification and else /*

Re: C++ PATCH for c++/91548 - fix detecting modifying const objects for ARRAY_REF

On 10/23/19 2:10 PM, Marek Polacek wrote: This fixes a bogus "modifying a const object" error for an array that actually isn't declared const. The problem was how I handled ARRAY_REFs here; we shouldn't look at the ARRAY_REF itself, but at the array its accessing. Bootstrapped/regtested on

Re: [C++ Patch] Improve build_x_unary_op locations

On 10/22/19 2:52 PM, Marek Polacek wrote: On Tue, Oct 22, 2019 at 08:48:30PM +0200, Paolo Carlini wrote: Hi, at the moment I'm going through more typeck.c and typeck2.c functions: the below are some straightforward changes for build_x_unary_op (fwiw, the resulting locations are also consistent

Re: [C++ PATCH] Partial fix for a recent regression (PR c++/90947)

On 10/22/19 11:03 AM, Jakub Jelinek wrote: Hi! The following patch is just a partial fix for a regression introduced in the PR90947 changes, the testcase is fixed for just C++17/20. type_initializer_zero_p has been added to the generic code, supposedly because similar initializer_zerop is in

Re: [PATCH] Add iterator concepts and range access customization points for C++20

On 29/10/19 17:43 +, Jonathan Wakely wrote: This adds most of the new C++20 features to , as well as a few initial pieces of (but no actual header just yet). I broke Clang again with this. Fixed by the attached patch. Tested powerpc64le-linux, committed to trunk. commit

Re: [PATCH] PR c++/91369 Implement P0784R7 changes to allocation and construction

On 29/10/19 09:37 +, Jonathan Wakely wrote: On 29/10/19 10:23 +0100, Stephan Bergmann wrote: On 23/10/2019 21:27, Jonathan Wakely wrote: This patch is the first part of library support for constexpr std::vector and std::string. This only includes the changes to std::allocator,

Re: Deprecating cc0 (and consequently cc0 targets)

On 10/29/19 6:26 AM, John Paul Adrian Glaubitz wrote: > Hello! > > We have raised $5000 to support anyone willing to work on this for the > m68k target [1]. We really need the m68k to stay as it's essential to > be able to compile for Linux/m68k, NetBSD/m68k and AROS/m68k (a new > and

[RFC PATCH] targetm.omp.device_kind_arch_isa and OpenMP declare variant kind/arch/isa handling

Hi! The following patch attempts to implement the OpenMP declare variant (and later on metadirective) device set arch/isa selectors. The standard makes it implementation defined what an arch is and what is isa, but I think because there is no selector like target that arch should mostly contain

[PATCH] Minor improvements to testsuite iterator utilities

* testsuite/util/testsuite_iterators.h (BoundsContainer::size()): Add new member function. (WritableObject::operator=): Constrain with enable_if when available. (remove_cv): Use std::remove_if when available. (test_container::it(int)): Use size().

[PATCH] PR libstdc++/92267 fix ABI change in deque iterators

Defaulting the copy constructor on its first declaration made it change from user-provided (and non-trivial) to implicitly-defined (and trivial). This caused an ABI incompatibility between GCC 8 and GCC 9, where functions taking a deque iterator disagree on the argument passing convention.

[16/n] Apply maximum nunits for BB SLP

The BB vectoriser picked vector types in the same way as the loop vectoriser: it picked a vector mode/size for the region and then based all the vector types off that choice. This meant we could end up trying to use vector types that had too many elements for the group size. The main part of

[15/n] Consider building nodes from scalars in vect_slp_analyze_node_operations

If the statements in an SLP node aren't similar enough to be vectorised, or aren't something the vectoriser has code to handle, the BB vectoriser tries building the vector from scalars instead. This patch does the same thing if we're able to build a viable-looking tree but fail later during the

[committed] disable c-c++-common/Warray-bounds-4.c to avoid PR 83543

Some of the string tests I've been adding have a tendency to fail on some targets as a result of PR 83543 which prevents GCC from determining the length of constant strings used to initialize local aggregates over some size (the size varies from target to target). I tend to forget about this

Re: [Patch][Demangler] Fix for complex values

There seems to be a small issue with the commit, somehow "float _Complex" turned into "Complex" within "demangle-expected", so the test now fails. Attached will be a fix for it. Thank you for committing the fix though. Miguel >From 7eb6afb42ff1ce1c22f0fce167c3fb593d316abb Mon Sep 17 00:00:00

Re: [PR47785] COLLECT_AS_OPTIONS

On Sun, Oct 27, 2019 at 6:33 PM Kugan Vivekanandarajah wrote: > > Hi Richard, > > Thanks for the review. > > On Wed, 23 Oct 2019 at 23:07, Richard Biener > wrote: > > > > On Mon, Oct 21, 2019 at 10:04 AM Kugan Vivekanandarajah > > wrote: > > > > > > Hi Richard, > > > > > > Thanks for the

[PATCH] Fix PR65930

The following fixes the last testcase (actually the first) missing in the PR showing missed reduction vectorization with sign-changes in place. Actually we already vectorize the first testcase now but fail to use a SLP reduction group which pessimizes code-generation. Bootstrapped on

Re: [PATCH][RFC] C++-style iterators for FOR_EACH_IMM_USE_STMT

On Tue, 2019-10-29 at 11:26 +0100, Richard Biener wrote: > While I converted other iterators requiring special BREAK_FROM_XYZ > a few years ago FOR_EACH_IMM_USE_STMT is remaining. I've pondered > a bit but cannot arrive at a "nice" solution here with just one > iterator as the macros happen to

Re: [PATCH] Prevent LTO section collision for a symbol name starting with '*'.

> gcc/cgraph.c | 14 ++ > gcc/cgraphclones.c | 5 + > gcc/ipa-fnsummary.c | 2 +- > gcc/ipa-hsa.c| 2 +- > gcc/ipa-icf.c| 2 +- > gcc/ipa-prop.c |

Re: [PATCH] Pass memory statistics for {symbol,call}_summary.

> Hi. > > The pass passes memory allocation location to underlying > hash_map (and vec). > > Patch can bootstrap on x86_64-linux-gnu and survives regression tests. > > Ready to be installed? OK, thanks! Honza > Thanks, > Martin > > gcc/ChangeLog: > > 2019-10-29 Martin Liska > > *

Re: [PATCH] Release function and edge summaries allocated with GGC.

> Hi. > > There's updated version that puts back vec_free to destructors. > It's necessary to properly release memory. > > Patch can bootstrap on x86_64-linux-gnu and survives regression tests. > > Ready to be installed? OK, thanks! (I will also check it on firefox memory stats) Honza > Thanks,

[PATCH] Fix PR92260

The following fixes the PR. Bootstrapped and tested on x86_64-unknown-linux-gnu, applied. Richard. 2019-10-29 Richard Biener PR tree-optimization/92260 * tree-vect-slp.c (vect_get_constant_vectors): Special-case lane-reducing ops. * gcc.dg/pr92260.c: New

Re: [committed][vect]PR 88915: Vectorize epilogues when versioning loops (was Re: [PATCH 1/2][vect]PR 88915: Vectorize epilogues when versioning loops)

On Tue, 29 Oct 2019, Andre Vieira (lists) wrote: > Hi richi, > > > Committed the patch with the suggested change in revision r277569. > > I will look at the follow-up, from what I understood the idea was to add a > field to the dr_vec_info where we keep the "extra-offset" that represents the >

[PATCH] Pass memory statistics for {symbol,call}_summary.

Hi. The pass passes memory allocation location to underlying hash_map (and vec). Patch can bootstrap on x86_64-linux-gnu and survives regression tests. Ready to be installed? Thanks, Martin gcc/ChangeLog: 2019-10-29 Martin Liska * symbol-summary.h (function_summary): Pass memory

[committed][vect]PR 88915: Vectorize epilogues when versioning loops (was Re: [PATCH 1/2][vect]PR 88915: Vectorize epilogues when versioning loops)

Hi richi, Committed the patch with the suggested change in revision r277569. I will look at the follow-up, from what I understood the idea was to add a field to the dr_vec_info where we keep the "extra-offset" that represents the position in the DR wrt the current loop/epilogue. So when we

[PATCH 0/2] cgraph_node refactoring

Hi. The patch is about refactoring of cgraph_node where I removed 2 embedded structs with just few members. Patch can bootstrap on x86_64-linux-gnu and survives regression tests. Ready to be installed? Thanks, Martin Martin Liska (2): Remove cgraph_global_info. Remove cgraph_local_info

[PATCH 2/2] Remove cgraph_local_info structure.

gcc/ChangeLog: 2019-10-25 Martin Liska * cgraph.c (cgraph_node::local_info): Transform to ... (cgraph_node::local_info_node): ... this. (cgraph_node::dump): Remove cgraph_local_info and put its fields directly into cgraph_node.

[PATCH 1/2] Remove cgraph_global_info.

--- gcc/cgraph.c | 56 - gcc/cgraph.h | 41 --- gcc/cgraphbuild.c | 2 +- gcc/cgraphclones.c | 7 ++-- gcc/cgraphunit.c | 16 gcc/gimple-fold.c | 4 +- gcc/ipa-comdats.c |

Re: [PATCH] Release function and edge summaries allocated with GGC.

Hi. There's updated version that puts back vec_free to destructors. It's necessary to properly release memory. Patch can bootstrap on x86_64-linux-gnu and survives regression tests. Ready to be installed? Thanks, Martin From 8faffc371e5cc3610f18ff1e65f7f14af397233a Mon Sep 17 00:00:00 2001

[PATCH v2] PR85678: Change default to -fno-common

v2: Tweak testsuite options to avoid failures GCC currently defaults to -fcommon. As discussed in the PR, this is an ancient C feature which is not conforming with the latest C standards. On many targets this means global variable accesses have a codesize and performance penalty. This applies

Re: Deprecating cc0 (and consequently cc0 targets)

Hello! On September 20, 2019 5:38:38 PM GMT+02:00, Jeff Law wrote: >So this message is serving as official notice that we are *deprecating* >all cc0 support in gcc-10. We are not removing any code or targets at >this time -- removals would happen during the gcc-11 cycle. > > >avr >cris >h8300

Re: [PATCH] PR85678: Change default to -fno-common

Hi Wilco, Wilco Dijkstra wrote: >> Testsuite fails are order “a few hundred” mostly seem to be related to >> tree-prof >> and vector tests (plus the anticipated scan-asm stuff, where code-gen will >> have >> changed). I don’t have cycles to analyse the causes right now - but that >> gives

Re: [PATCH] Report errors on inconsistent OpenACC nested reduction clauses

On 24.10.19 16:31, Thomas Schwinge wrote: Hi, I have attached a revised patch. [...] I was wondering if the way in which the patch avoids issuing errors about operator switches more than once by modifying the clauses (cf. the corresponding comment in omp-low.c) could lead to problems [...]

Re: [PATCH] OpenACC reference count overhaul

Hi! This is a new version of the patch which hopefully addresses all review comments. Further commentary below. On Mon, 21 Oct 2019 16:14:11 +0200 Thomas Schwinge wrote: > On 2019-10-03T09:35:04-0700, Julian Brown > wrote: > > This patch has been broken out of the patch supporting OpenACC 2.6

Re: [PATCH] PR85678: Change default to -fno-common

Hi Iain, > for the record,  Darwin bootstraps OK with the change (which is to be > expected, > since the preferred setting for it is -fno-common). That's good to hear. > Testsuite fails are order “a few hundred” mostly seem to be related to > tree-prof > and vector tests (plus the anticipated

Re: [PATCH 1/2][vect]PR 88915: Vectorize epilogues when versioning loops

On Mon, 28 Oct 2019, Andre Vieira (lists) wrote: > Hi, > > Reworked according to your comments, see inline for clarification. > > Is this OK for trunk? + gimple_seq seq = STMT_VINFO_PATTERN_DEF_SEQ (stmt_vinfo); + while (seq) + { +

Re: [PATCH] Restrict LOOP_ALIGN to loop headers only.

On 8/9/19 2:51 PM, Martin Liška wrote: > On 8/9/19 2:13 PM, Michael Matz wrote: >> Hi, >> >> On Fri, 9 Aug 2019, Richard Biener wrote: >> >>> Of course I'm still afraid that the other code exists for a reason >>> (tuning/hack/whatever...). >>> >>> Note that with the patch we're now applying

Re: [PATCH] Fix another of the PR65930 reduction cases

On Tue, 29 Oct 2019, Bernhard Reutner-Fischer wrote: > On 29 October 2019 10:36:47 CET, Richard Biener wrote: > >On Tue, 29 Oct 2019, Bernhard Reutner-Fischer wrote: > > > > > >Unfortunately it's not semantically equivalent ;) I could indeed > >break once cnt reaches 2 but not sure if it's

Re: [PATCH] Prevent LTO section collision for a symbol name starting with '*'.

On 10/22/19 1:09 PM, Martin Liška wrote: > @Honza: PING^1 > > On 9/18/19 12:14 PM, Martin Liška wrote: >> On 9/11/19 1:38 PM, Martin Liška wrote: >>> The inline_clone manipulation happens in cgraph_node::find_replacement where >>> we manipulate the clone_of. >> >> I fixed that but there's a

[PATCH] Release function and edge summaries allocated with GGC.

Hi. The patch is about {symbol,edge}_summary simplification where ::release function is removed. Instead of it, one should use either delete operand (for heap summaries), or explicitly call destructor and ggc_free. Patch can bootstrap on x86_64-linux-gnu and survives regression tests. Ready to

Re: [PATCH] Fix another of the PR65930 reduction cases

On 29 October 2019 10:36:47 CET, Richard Biener wrote: >On Tue, 29 Oct 2019, Bernhard Reutner-Fischer wrote: > >Unfortunately it's not semantically equivalent ;) I could indeed >break once cnt reaches 2 but not sure if it's worth the ugliness ;) I managed to read cnt == 1 ;) So yep, not worth

Re: [Patch, fortran] PR fortran/92142 - CFI_setpointer corrupts descriptor

Hi, On 17/10/19 17:29, Tobias Burnus wrote: If you generate to stdout/stderr like in this case, I think it makes sense to also check for this output using "{dg-output …}". Added the suggested check and a few touches to comments and the error message. that might be a bug in the C code of

Re: [PATCH] Fix PR92162

On Tue, 29 Oct 2019, Richard Sandiford wrote: > Richard Biener writes: > > Bootstrapped and tested on x86_64-unknown-linux-gnu, applied. > > > > Richard. > > > > 2019-10-21 Richard Biener > > > > PR tree-optimization/92162 > > * tree-vect-loop.c (vect_create_epilog_for_reduction):

[PATCH][RFC] C++-style iterators for FOR_EACH_IMM_USE_STMT

While I converted other iterators requiring special BREAK_FROM_XYZ a few years ago FOR_EACH_IMM_USE_STMT is remaining. I've pondered a bit but cannot arrive at a "nice" solution here with just one iterator as the macros happen to use. For reference, the macro use is imm_use_iterator iter;

Re: [PATCH] Fix PR92162

Richard Biener writes: > Bootstrapped and tested on x86_64-unknown-linux-gnu, applied. > > Richard. > > 2019-10-21 Richard Biener > > PR tree-optimization/92162 > * tree-vect-loop.c (vect_create_epilog_for_reduction): Lookup > STMT_VINFO_REDUC_IDX in reduc_info. > *

Re: [PATCH] PR c++/91369 Implement P0784R7 changes to allocation and construction

On 29/10/19 10:23 +0100, Stephan Bergmann wrote: On 23/10/2019 21:27, Jonathan Wakely wrote: This patch is the first part of library support for constexpr std::vector and std::string. This only includes the changes to std::allocator, std::allocator_traits, std::construct_at, std::destroy_at,

Re: [PATCH] Fix another of the PR65930 reduction cases

On Tue, 29 Oct 2019, Bernhard Reutner-Fischer wrote: > On Mon, 28 Oct 2019 14:55:37 +0100 (CET) > Richard Biener wrote: > > > Index: gcc/tree-vect-loop.c > > === > > --- gcc/tree-vect-loop.c(revision 277517) > > +++

Re: [PATCH] PR c++/91369 Implement P0784R7 changes to allocation and construction

On 23/10/2019 21:27, Jonathan Wakely wrote: This patch is the first part of library support for constexpr std::vector and std::string. This only includes the changes to std::allocator, std::allocator_traits, std::construct_at, std::destroy_at, std::destroy and std::destroy_n. [...] Tested

Re: [12/32] Remove global call sets: cselib.c

On 9/29/19 11:05 PM, Jeff Law wrote: > On 9/11/19 1:09 PM, Richard Sandiford wrote: >> cselib_invalidate_regno is a no-op if REG_VALUES (i) is null, >> so we can check that first. Then, if we know what mode the register >> currently has, we can check whether it's clobbered in that mode. >> >>

[committed][AArch64] Add support for the SVE PCS

The AAPCS64 specifies that if a function takes arguments in SVE registers or returns them in SVE registers, it must preserve all of Z8-Z23 and all of P4-P11. (Normal functions only preserve the low 64 bits of Z8-Z15 and clobber all of the predicate registers.) This variation is known informally

[Patch][Fortran] PR 92208 don't use function-result dummy variable as actual argument

For code like:    call foo(char_array=bar()) gfortran was using the symbol of the (hidden) result-string-length dummy argument of "bar" ("..__result") as (hidden) string-length actual argument when calling "foo". Naturally, the middle end was not amused and gave an ICE (with GCC 9 + 10). For

Re: [PATCH] rs6000: Refine implicit funroll-loops with unroll_adjust hook.

Richard Biener writes: > On Tue, 29 Oct 2019, Jiufu Guo wrote: > >> Jiufu Guo writes: >> >> > Hi, >> > >> > In previous patch r277501, which is changing PARAM_MAX_UNROLL_TIMES >> > and PARAM_MAX_UNROLLED_INSNS values during option overriding, while >> > it would better to use target loop

Re: [PATCH] rs6000: Enable limited unrolling at -O2

Richard Biener writes: > On Mon, 28 Oct 2019, Jiufu Guo wrote: > >> Richard Biener writes: >> >> > On Fri, 25 Oct 2019, Jiufu Guo wrote: >> > >> >> Hi, >> >> >> >> In PR88760, there are a few disscussion about improve or tune unroller for >> >> targets. And we would agree to enable unroller

Re: [PATCH] rs6000: Refine implicit funroll-loops with unroll_adjust hook.

On Tue, 29 Oct 2019, Jiufu Guo wrote: > Jiufu Guo writes: > > > Hi, > > > > In previous patch r277501, which is changing PARAM_MAX_UNROLL_TIMES > > and PARAM_MAX_UNROLLED_INSNS values during option overriding, while > > it would better to use target loop unroll adjust hook. The hook can > >

Re: [PR47785] COLLECT_AS_OPTIONS

On Tue, Oct 29, 2019 at 8:26 AM Bernhard Reutner-Fischer wrote: > > On 28 October 2019 23:08:10 CET, Richard Earnshaw > wrote: > >On 28/10/2019 21:52, Bernhard Reutner-Fischer wrote: > >> On Mon, 28 Oct 2019 11:53:06 +1100 > >> Kugan Vivekanandarajah wrote: > >> > >>> On Wed, 23 Oct 2019 at

Re: [PATCH] rs6000: Refine implicit funroll-loops with unroll_adjust hook.

Jiufu Guo writes: > Hi, > > In previous patch r277501, which is changing PARAM_MAX_UNROLL_TIMES > and PARAM_MAX_UNROLLED_INSNS values during option overriding, while > it would better to use target loop unroll adjust hook. The hook can > also help to do further target related hueristic adjust. >

Re: [PATCH] Fix another of the PR65930 reduction cases

On Mon, 28 Oct 2019 14:55:37 +0100 (CET) Richard Biener wrote: > Index: gcc/tree-vect-loop.c > === > --- gcc/tree-vect-loop.c (revision 277517) > +++ gcc/tree-vect-loop.c (working copy) > @@ -2690,6 +2689,20 @@ pop: >

[committed][AArch64] Extend SVE reverse permutes to predicates

This is tested by the main SVE ACLE patches, but since it affects the evpc routines, it seemed worth splitting out. Tested on aarch64-linux-gnu (with and without SVE) and aarch64_be-elf. Applied as r277562. Richard 2019-10-29 Richard Sandiford gcc/ * config/aarch64/aarch64-sve.md

[committed][AArch64] Add FFR and FFRT registers

This patch adds the First Fault Register to the AArch64 port, as well as a fake register known as the FFR Token or FFRT. The main ACLE patch explains what the FFRT does and how it works. Tested on aarch64-linux-gnu (with and without SVE) and aarch64_be-elf. Applied as r277561. Richard

[committed][AArch64] Handle scalars in cmp and shift immediate queries

The SVE ACLE has convenience functions that take scalar arguments instead of vectors. This patch makes it easier to implement the shift and compare functions by making the associated immediate queries work for scalar immediates as well as vector duplicates of them. The "const" codes in the

[PATCH] rs6000: Refine implicit funroll-loops with unroll_adjust hook.

Hi, In previous patch r277501, which is changing PARAM_MAX_UNROLL_TIMES and PARAM_MAX_UNROLLED_INSNS values during option overriding, while it would better to use target loop unroll adjust hook. The hook can also help to do further target related hueristic adjust. This patch is adding target loop

Re: [PATCH] PR85678: Change default to -fno-common

On Mon, Oct 28, 2019 at 10:39 PM Iain Sandoe wrote: > > Wilco Dijkstra wrote: > >>> > >>> I suppose targets can override this decision. > >> I think they probably could via the override_options mechanism. > > > > Yes, it's trivial to add this to target_option_override(): > > > > if

[PATCH] New testcase for PR92228

Committed. Richard. 2019-10-29 Richard Biener PR tree-optimization/92241 * gcc.dg/torture/pr92241-2.c: New testcase. Index: gcc/testsuite/gcc.dg/torture/pr92241-2.c === ---

Content Collaboration

Hello! I hope things are going great with you. I’m Tara Smith, and I'm working as a member of Kite ’s Editorial Team. Kite is an AI Autocomplete plugin for Python that allows programmers to offload the repetitive parts of writing code. We believe that machine learning will

[PATCH] Don't mention MMX in -msse etc. option descriptions

Hi! While working on the OpenMP isa patch, I've noticed most of the x86 ISA options imply in the help text that it enables MMX, when they do not. We now have the mmx in sse2, so to some extent most of the built-in functions are enabled with sse2 on 64-bit targets, but we do not enable MMX code

[committed] Fix install.texi typo

Hi! I have noticed a typo in spelling of the configure option in the example. Furthermore, it was listing targets that are not realy offload target, so this patch changed them to really supported offload targets. Bootstrapped on x86_64-linux and i686-linux, committed to trunk as obvious.

Re: [PR47785] COLLECT_AS_OPTIONS

On 28 October 2019 23:08:10 CET, Richard Earnshaw wrote: >On 28/10/2019 21:52, Bernhard Reutner-Fischer wrote: >> On Mon, 28 Oct 2019 11:53:06 +1100 >> Kugan Vivekanandarajah wrote: >> >>> On Wed, 23 Oct 2019 at 23:07, Richard Biener > wrote: >> Did you try this with multiple assembler