[PATCH, V3, #9 of 10], Prefixed addressing tests with large offsets

This patch contains the tests for prefixed addressing with large offsets. It is exactly the same as patch V1 #9. When I add patches 8-10 to the testsuite, all of these tests now run. Once I have checked in the previous patches, can I check this patch into the trunk? (note, the new files were

Re: Warray-bounds-39 vs recent c_strlen changes

On 8/26/19 12:19 PM, Martin Sebor wrote: > On 8/26/19 11:41 AM, Jeff Law wrote: >> I think we need to go back and revisit this hunk: >> >>>    /* If the offset is known to be out of bounds, warn, and call >>> strlen at >>>   runtime.  */ >>>    if (eltoff < 0 || eltoff >= maxelts) >>> {

[PATCH, V3, #10 of #10], Pc-relative tests

This patch contains the pc-relative tests for GCC. It is exactly the same as patch V1 #10. When I add patches 8-10 to the testsuite, all of these tests now run. Once I have checked in the previous patches, can I check this patch into the trunk? (note, the new files were created in the branch

[PATCH, V3, #8 of 10], Miscellaneous prefixed addressing tests

This patch contains the miscellaneous tests for GCC to test some features of prefixed addressing. It is exactly the same as patch V1 #8. When I add patches 8-10 to the testsuite, all of these tests now run. Once I have checked in the previous patches, can I check this patch into the trunk?

[PATCH, V3, #7 of 10], Implement PCREL_OPT relocation optimization

This patch is a slight rework on V1 patch #7 (V1 patch #6 is not going to be re-submitted at this time). This patch adds a new RTL pass that supports creating the optimization and flagging the appropriate load of external pc-relative addresses and the use of that address in the basic block. Here

[wwwdocs] codingconventions.html - remove libjava/classpath reference

Now sure how this could survive when GCJ/libjava were removed. Committed. Gerald Index: codingconventions.html === RCS file: /cvs/gcc/wwwdocs/htdocs/codingconventions.html,v retrieving revision 1.91 diff -u -r1.91

[PATCH, V3, #6 of 10], Fix vec_extract breakage

This patch fixes the bug I mentioned in a previous patch, i.e. #include static vector double v; // ... double foo (int n) { double x = vec_extract (v, n); return x; } would generate incorrect code because it only has one

[PR fortran/91496] !GCC$ directives error if mistyped or unknown

Dear all, the attached patch adds Fortran support for the following pragmas (loop annotations): IVDEP (ignore vector dependencies), VECTOR, and NOVECTOR. Furthermore, it downgrades unsupported directives from error to warning (by default, it stays an error with -pedantic), thus fixing the PR.

[PATCH, V3, #5 of 10], Make -mpcrel default on little endian Linux systems

I rewrote the simple previous patch (V1 #5) to enable pc-relative addressing by default, to only enable by default on little endian Linux systems. Other systems like AIX and BSD will default to not supporting prefixed addressing until they are configured to support these addressing modes. I

Re: C++ PATCH for P1152R4: Deprecating some uses of volatile (PR c++/91361)

On Fri, Aug 23, 2019 at 07:39:57PM -0400, Marek Polacek wrote: > On Fri, Aug 23, 2019 at 02:43:42PM -0700, Jason Merrill wrote: > > On 8/23/19 9:32 AM, Marek Polacek wrote: > > > This patch implements another C++20 feature, partially deprecating > > > volatile. > > > You can read the proposal

[PATCH, V3, #4 of 10], Add general prefixed/pcrel support

This patch (V3 patch #4) is a rework of the V1 patches #3 and #4. It adds support to generate prefixed (and local pc-relative) instructions for all modes, except SDmode. SDmode can't be used with a prefixed offset instruction, because the default method to load up a SDmode value is to use the

[PATCH, V3, #2 of 10], Improve rs6000_setup_addr_mask

This patch is an optional patch. In previous patches, people said that the rs6000_setup_addr_mask function was hard to understand, exactly what address mask bits were set. This code attempts to make this clearer by moving the settings for GPRs, FPRs, and traditional Altivec registers to separate

[PATCH, V3, #3 of 10], Add prefixed RTL insn attribute

This patch adds the basic RTL insn attribute for doing prefixed and pc-relative addressing. It is fairly similar to the version 1 patch #2. This patch is an infrastructure patch that will be used by the next patch (#4) to use prefixed loads and stores where it is appropriate. In this patch, only

Re: [PATCH] Simplify and generalize rust-demangle's unescaping logic.

On Wed, Aug 14, 2019 at 10:24 AM Eduard-Mihai Burtescu wrote: > > Previously, rust-demangle.c was special-casing a fixed number > of '$uXY$' escapes, but 'XY' can technically be any hex value, > representing some Unicode codepoint. > > This patch adds more general support for '$u...$' escapes, >

Go patch committed: Generalize cleanup of unresolved placeholders

This patch to the Go frontend by Than McIntosh generalizes the cleanup of unresolved placeholder pointer types. This patch extends the work in https://golang.org/cl/51131 (https://gcc.gnu.org/ml/gcc-patches/2017-07/msg01934.html) to include placeholder pointer types created for Go function types,

[PATCH V3, #1 of 10], Add basic pc-relative support

This patch adds basic pc-relative support. I changed the public type used in the prefixed match function from insn_form to trad_form. This argument is used in matching prefixed addresses to say whether the traditional instruction's offset uses the D instruction format, the DS instruction format,

Re: PR 90409 Deque fiil/copy/move/copy_backward/move_backward/equal overloads

Hi     I am eventually working on another implementation to acheive the same result with less changes and codes. I think you'll prefer this one.     So don't spend any time on this patch proposal, a new one will come in a couple of days. François

[PING][PATCH] Simplify and generalize rust-demangle's unescaping logic.

Ping: https://gcc.gnu.org/ml/gcc-patches/2019-08/msg01007.html On Wed, Aug 14, 2019, at 8:22 PM, Eduard-Mihai Burtescu wrote: > Previously, rust-demangle.c was special-casing a fixed number > of '$uXY$' escapes, but 'XY' can technically be any hex value, > representing some Unicode codepoint. >

[PATCH, i386]: Fix gcc.target/i386/sse4_1-round-roundeven-2.c execution test failure

We have to negate masking value to clear certain bits. 2019-08-26 Uroš Bizjak * config/i386/i386.c (emit_i387_cw_initialization) : Fix masking operand value. Tested on x86_64-linux-gnu {,-m32} and committed to mainline SVN. Uros. Index: config/i386/i386.c

Re: Warray-bounds-39 vs recent c_strlen changes

On 8/26/19 11:41 AM, Jeff Law wrote: I think we need to go back and revisit this hunk: /* If the offset is known to be out of bounds, warn, and call strlen at runtime. */ if (eltoff < 0 || eltoff >= maxelts) { /* Suppress multiple warnings for propagated constant

Warray-bounds-39 vs recent c_strlen changes

I think we need to go back and revisit this hunk: > /* If the offset is known to be out of bounds, warn, and call strlen at > runtime. */ > if (eltoff < 0 || eltoff >= maxelts) > { > /* Suppress multiple warnings for propagated constant strings. */ > if (only_value != 2

PowerPC future machine, version 3

Since there was a version 2 of one of the previous patches, I'll call this set version 3. These patches completely replace the previous patches. As before, these are for a future PowerPC machine that we are looking at. If a real machine is announced that uses these instructions, we may change

[PATCH V3 05/11] bpf: new GCC port

This patch adds a port for the Linux kernel eBPF architecture to GCC. ChangeLog: * configure.ac: Support for bpf-*-* targets. * configure: Regenerate. contrib/ChangeLog: * config-list.mk (LIST): Disable go in bpf-*-* targets. gcc/ChangeLog: * config.gcc: Support for bpf-*-*

[PATCH V3 08/11] bpf: make target-supports.exp aware of eBPF

This patch makes the several effective target checks in target-supports.exp to be aware of eBPF targets. gcc/testsuite/ChangeLog: * lib/target-supports.exp (check_effective_target_trampolines): Adapt to eBPF. (check_effective_target_stack_size): Likewise.

[PATCH V3 11/11] bpf: add myself as the maintainer for the eBPF port

ChangeLog: * MAINTAINERS: Add myself as the maintainer of the eBPF port. Remove myself from Write After Approval section. --- ChangeLog | 5 + MAINTAINERS | 2 +- 2 files changed, 6 insertions(+), 1 deletion(-) diff --git a/MAINTAINERS b/MAINTAINERS index

[PATCH V3 10/11] bpf: manual updates for eBPF

gcc/ChangeLog: * doc/invoke.texi (Option Summary): Cover eBPF. (eBPF Options): New section. * doc/extend.texi (BPF Built-in Functions): Likewise. (BPF Kernel Helpers): Likewise. --- gcc/ChangeLog | 7 +++ gcc/doc/extend.texi | 171

[PATCH V3 07/11] bpf: gcc.target eBPF testsuite

This patch adds a new testsuite to gcc.target, with eBPF specific tests. Tests are included for: - Target specific diagnostics. - All built-in functions. testsuite/ChangeLog: * gcc.target/bpf/bpf.exp: New file. * gcc.target/bpf/builtin-load.c: Likewise. *

[PATCH V3 00/11] eBPF support for GCC

[Differences from V2: . Indentation fixes. . Trailing spaces fixes. . Regenerate configure scripts using vanilla 2.69. This time the configure diff is not included in the patch series. . Do not build libgcc2 with -O0. . Do not define INCLUDE_STRING in bpf.c . Do not initialize x_bpf_kernel in

[PATCH V3 09/11] bpf: adjust GCC testsuite to eBPF limitations

This patch makes many tests in gcc.dg and gcc.c-torture to be skipped in bpf-*-* targets. This is due to the many limitations imposed by eBPF to what would be perfectly valid C code: no support for more than 5 arguments to function calls, no support for indirect jumps, a very limited range for

[PATCH V3 06/11] bpf: new libgcc port

This patch adds an eBPF port to libgcc. As of today, compiled eBPF programs do not support a single-entry point schema. Instead, a BPF "executable" is a relocatable ELF object file containing multiple entry points, in certain named sections. Also, the BPF loaders in the kernel do not execute

[PATCH V3 03/11] testsuite: annotate c-torture/compile tests with dg-require-stack-size

This patch annotates tests that make use of a significant a mount of stack space. Embedded and other restricted targets may have problems compiling and running these tests. Note that the annotations are in many cases not exact. testsuite/ChangeLog: * gcc.c-torture/compile/2609-1.c:

[PATCH V3 02/11] opt-functions.awk: fix comparison of limit, begin and end

The function integer_range_info makes sure that, if provided, the initial value fills in the especified range. However, it is necessary to convert the values to a numerical context before comparing, to make sure awk is using arithmetical order and not lexicographical order. gcc/ChangeLog:

[PATCH V3 01/11] Update config.sub and config.guess.

* config.sub: Import upstream version 2019-06-30. * config.guess: Import upstream version 2019-07-24. --- ChangeLog| 5 ++ config.guess | 264 +++ config.sub | 50 +-- 3 files changed, 240 insertions(+), 79

[PATCH V3 04/11] testsuite: new require effective target indirect_calls

This patch adds a new dg_require_effective_target procedure to the testsuite infrastructure: indirect_calls. This new function tells whether a target supports calls to non-constant call targets. This patch also annotates the tests in the gcc.c-torture testuite that require support for indirect

Re: [PATCH] Fix new clang warnings.

On 8/26/19 1:47 AM, Martin Liška wrote: > Hi. > > The patch address 2 new warning seen by clang (and clang-static-analyzer) > and changes are explained in the ChangeLog entry. > > Patch can bootstrap on x86_64-linux-gnu and survives regression tests. > > Ready to be installed? > Thanks, >

Re: [Patch][PR91504] Inlining misses some logical operation folding

On Mon, Aug 26, 2019 at 02:04:25PM +0200, Richard Biener wrote: > On Mon, 26 Aug 2019, kamlesh kumar wrote: > > +/* (~a & b) ^ a --> (a | b) */ > > +(simplify > > + (bit_xor:c (bit_and:cs (bit_not @0) @1) @0) > > + (bit_ior @0 @1)) > > + > > Are you sure? > > (~1804289383 & 846930886) ^

Re: [PATCH v2 3/9] Introduce can_vector_compare_p function

> Am 26.08.2019 um 15:17 schrieb Ilya Leoshkevich : > >> Am 26.08.2019 um 15:06 schrieb Richard Biener : >> >> On Mon, Aug 26, 2019 at 1:54 PM Ilya Leoshkevich wrote: >>> Am 26.08.2019 um 10:49 schrieb Richard Biener : On Fri, Aug 23, 2019 at 1:35 PM Ilya Leoshkevich

Re: C++ PATCH for c++/91545 - ICE in constexpr store evaluation

OK. On Mon, Aug 26, 2019 at 9:35 AM Marek Polacek wrote: > Now that DECL_MUTABLE_P checks that it got a FIELD_DECL node, One Does Not > Simply Check DECL_P. For an ARRAY_REF, "elt" can be a VAR_DECL. > > Bootstrapped/regtested on x86_64-linux, ok for trunk? > > 2019-08-26 Marek Polacek > >

Re: [wwwdocs] Reflect __builtin_roundeven in gcc-10/changes.html

On Mon, 26 Aug 2019, Martin Jambor wrote: > would the following be a good way to state in changes.html that we > can fold __builtin_roundeven and expand it on an x86? > +The following built-in functions have been introduced. > + > + __builtin_roundeven for the corresponding function from > +

[wwwdocs] Reflect __builtin_roundeven in gcc-10/changes.html

Hi Gerald, would the following be a good way to state in changes.html that we can fold __builtin_roundeven and expand it on an x86? Thanks, Martin Index: gcc-10/changes.html === RCS file:

Re: [PATCH][i386][STV] Remove general_remove_non_convertible_regs

On Mon, Aug 26, 2019 at 3:39 PM Richard Biener wrote: > > > The following removes the no longer necessary > general_remove_non_convertible_regs since we can now deal with > chains which define pseudos also defined outside of the chain. > > Bootstrapped and tested on x86_64-unknown-linux-gnu, OK?

[PATCH][i386][STV] Remove general_remove_non_convertible_regs

The following removes the no longer necessary general_remove_non_convertible_regs since we can now deal with chains which define pseudos also defined outside of the chain. Bootstrapped and tested on x86_64-unknown-linux-gnu, OK? Thanks, Richard. 2019-08-26 Richard Biener *

C++ PATCH for c++/91545 - ICE in constexpr store evaluation

Now that DECL_MUTABLE_P checks that it got a FIELD_DECL node, One Does Not Simply Check DECL_P. For an ARRAY_REF, "elt" can be a VAR_DECL. Bootstrapped/regtested on x86_64-linux, ok for trunk? 2019-08-26 Marek Polacek PR c++/91545 - ICE in constexpr store evaluation. *

Re: [PATCH v2 3/9] Introduce can_vector_compare_p function

> Am 26.08.2019 um 15:06 schrieb Richard Biener : > > On Mon, Aug 26, 2019 at 1:54 PM Ilya Leoshkevich wrote: >> >>> Am 26.08.2019 um 10:49 schrieb Richard Biener : >>> >>> On Fri, Aug 23, 2019 at 1:35 PM Ilya Leoshkevich wrote: > Am 23.08.2019 um 13:24 schrieb Richard Biener >

Re: [PATCH v2 3/9] Introduce can_vector_compare_p function

On Mon, Aug 26, 2019 at 1:54 PM Ilya Leoshkevich wrote: > > > Am 26.08.2019 um 10:49 schrieb Richard Biener : > > > > On Fri, Aug 23, 2019 at 1:35 PM Ilya Leoshkevich wrote: > >> > >>> Am 23.08.2019 um 13:24 schrieb Richard Biener > >>> : > >>> > >>> On Fri, Aug 23, 2019 at 12:43 PM Richard

Re: [SVE] PR86753

On Mon, 26 Aug 2019 at 14:48, Richard Biener wrote: > > On Sun, Aug 25, 2019 at 11:13 PM Prathamesh Kulkarni > wrote: > > > > On Fri, 23 Aug 2019 at 19:43, Richard Sandiford > > wrote: > > > > > > Prathamesh Kulkarni writes: > > > > On Fri, 23 Aug 2019 at 18:15, Richard Sandiford > > > >

Re: [RFC PATCH, i386]: Improve STV pass by correcting the cost of moves to/from XMM reg

On Mon, 26 Aug 2019, Uros Bizjak wrote: > On Mon, Aug 26, 2019 at 2:11 PM Uros Bizjak wrote: > > > > On Mon, Aug 26, 2019 at 1:46 PM Richard Biener wrote: > > > > > > On Fri, 23 Aug 2019, Uros Bizjak wrote: > > > > > > > On Fri, Aug 23, 2019 at 1:52 PM Richard Biener > > > > wrote: > > > > >

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

On Fri, 23 Aug 2019, Andre Vieira (lists) wrote: > Hi, > > This patch is an improvement on my last RFC. As you pointed out, we can do > the vectorization analysis of the epilogues before doing the transformation, > using the same approach as used by openmp simd. I have not yet incorporated >

Re: [PATCH] Come up with json::integer_number and use it in GCOV.

PING^1 On 8/13/19 1:51 PM, Martin Liška wrote: > On 8/2/19 2:40 PM, David Malcolm wrote: >> Something that occurred to me reading the updated patch: maybe it would >> make things easier to have utility member functions of json::object to >> implicitly make the child, e.g.: >> >> void >>

Re: [RFC PATCH, i386]: Improve STV pass by correcting the cost of moves to/from XMM reg

On Mon, Aug 26, 2019 at 2:11 PM Uros Bizjak wrote: > > On Mon, Aug 26, 2019 at 1:46 PM Richard Biener wrote: > > > > On Fri, 23 Aug 2019, Uros Bizjak wrote: > > > > > On Fri, Aug 23, 2019 at 1:52 PM Richard Biener wrote: > > > > > > > > On Fri, 23 Aug 2019, Uros Bizjak wrote: > > > > > > > > >

Re: [PATCH resend 1/2] PR c/65403 - Ignore -Wno-error=

On 8/23/19 6:52 PM, Alex Henrie wrote: > On Fri, Aug 23, 2019 at 3:13 AM Martin Liška wrote: >> On 8/23/19 6:17 AM, Alex Henrie wrote: >>> +vec ignored_wnoerror_options; >> >> Here you'll need to add a comment. > > The declaration of ignored_options in opts-global.c doesn't have a > comment

Re: [PATCH 2/2][vect]Make vect-epilogues-nomask=1 default

On Fri, 23 Aug 2019, Andre Vieira (lists) wrote: > Hi, > > In this patch I turn epilogue vectorization on by default. I had to make > changes to the tests since the vectorizer dumps now show the analysis for both > the first and second vectorization. This required checks like >

[PING] [MIPS] Fix handling of MSA SUBREG moves on big-endian targets

Ping for https://gcc.gnu.org/ml/gcc-patches/2019-08/msg00539.html Cheers, Mihailo

Re: [RFC PATCH, i386]: Improve STV pass by correcting the cost of moves to/from XMM reg

On Mon, Aug 26, 2019 at 1:46 PM Richard Biener wrote: > > On Fri, 23 Aug 2019, Uros Bizjak wrote: > > > On Fri, Aug 23, 2019 at 1:52 PM Richard Biener wrote: > > > > > > On Fri, 23 Aug 2019, Uros Bizjak wrote: > > > > > > > This is currently a heads-up patch that removes the minimum limitation >

Re: [Patch][PR91504] Inlining misses some logical operation folding

On Mon, 26 Aug 2019, kamlesh kumar wrote: > 2019-08-26 Kamlesh Kumar > > * gcc/match.pd: Added simplification > pattern. > * gcc.dg/tree-ssa/pr91504.c: New test. > > > diff --git a/gcc/match.pd b/gcc/match.pd > index 93dcef9..b3734f8 100644 > ---

Re: [PATCH v2 3/9] Introduce can_vector_compare_p function

> Am 26.08.2019 um 10:49 schrieb Richard Biener : > > On Fri, Aug 23, 2019 at 1:35 PM Ilya Leoshkevich wrote: >> >>> Am 23.08.2019 um 13:24 schrieb Richard Biener : >>> >>> On Fri, Aug 23, 2019 at 12:43 PM Richard Sandiford >>> wrote: Ilya Leoshkevich writes: > @@ -3819,6

Re: [RFC PATCH, i386]: Improve STV pass by correcting the cost of moves to/from XMM reg

On Fri, 23 Aug 2019, Uros Bizjak wrote: > On Fri, Aug 23, 2019 at 1:52 PM Richard Biener wrote: > > > > On Fri, 23 Aug 2019, Uros Bizjak wrote: > > > > > This is currently a heads-up patch that removes the minimum limitation > > > of cost of moves to/from XMM reg. The immediate benefit is the

Re: [C++ PATCH] vfunc overrider simplification

On 8/25/19 2:35 PM, Jason Merrill wrote: On Sat, Aug 24, 2019 at 6:43 PM Nathan Sidwell > wrote: On 8/23/19 3:24 PM, Nathan Sidwell wrote: > In fixing a vfunc override bug on the modules branch, I noticed that > check_for_override can simply check

Re: [PATCH] Fix PR91522

On Mon, Aug 26, 2019 at 10:40 AM Richard Biener wrote: > > On Fri, 23 Aug 2019, Richard Biener wrote: > > > On Fri, 23 Aug 2019, Richard Biener wrote: > > > > > On Fri, 23 Aug 2019, Uros Bizjak wrote: > > > > > > > On Thu, Aug 22, 2019 at 3:35 PM Richard Biener > > > > wrote: > > > > > > > > >

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

Ok. I have a semi-working patch that has issues for inline clones. When we call cgraph_node::get_untransformed_body for an inline clone, then one needs to use clone_of->order to find proper LTO stream. What's more problematic is that such clone can be expanded: f/12 (f) @0x7769f708 Type:

Re: [SVE] PR86753

On Sun, Aug 25, 2019 at 11:13 PM Prathamesh Kulkarni wrote: > > On Fri, 23 Aug 2019 at 19:43, Richard Sandiford > wrote: > > > > Prathamesh Kulkarni writes: > > > On Fri, 23 Aug 2019 at 18:15, Richard Sandiford > > > wrote: > > >> > > >> Prathamesh Kulkarni writes: > > >> > On Thu, 22 Aug

Re: [PATCH][ARM] Cleanup logical DImode operations

On Thu, 22 Aug 2019 at 14:03, Kyrill Tkachov wrote: > > Hi Wilco, > > On 7/19/19 12:30 PM, Wilco Dijkstra wrote: > > > > Cleanup the logical DImode operations since the current implementation > > is way > > too complicated. Thumb-1, Thumb-2, VFP/Neon and iwMMXt all work > > differently, > >

Re: [RFA] [tree-optimization/80576] Handle non-constant sizes in DSE

On Fri, Aug 23, 2019 at 9:19 PM Jeff Law wrote: > > On 8/22/19 4:46 AM, Richard Biener wrote: > >>> Also you seem to use this info to constrain optimization when you > >>> might remember that types of addresses do not carry such information... > >>> Thus it should be "trivially" possible to write

Re: [PATCH v2 3/9] Introduce can_vector_compare_p function

On Fri, Aug 23, 2019 at 1:35 PM Ilya Leoshkevich wrote: > > > Am 23.08.2019 um 13:24 schrieb Richard Biener : > > > > On Fri, Aug 23, 2019 at 12:43 PM Richard Sandiford > > wrote: > >> > >> Ilya Leoshkevich writes: > >>> @@ -3819,6 +3820,82 @@ can_compare_p (enum rtx_code code, machine_mode >

Re: [PATCH] Fix PR91522

On Fri, 23 Aug 2019, Richard Biener wrote: > On Fri, 23 Aug 2019, Richard Biener wrote: > > > On Fri, 23 Aug 2019, Uros Bizjak wrote: > > > > > On Thu, Aug 22, 2019 at 3:35 PM Richard Biener wrote: > > > > > > > > > > > > This fixes quadraticness in STV and makes > > > > > > > > machine dep

Re: [patch, fortran] Introduce -fallow-argument-mismatch

On Sun, Aug 25, 2019 at 2:16 PM Thomas Koenig wrote: > > Hello world, > > attached is a patch introducing the -fallow-argument-mismatch > option, to separate this from the general kitchen sink -std=legacy. > As discussed, this can only be turned off by -w. > > Regression-tested on

[PATCH] Fix new clang warnings.

Hi. The patch address 2 new warning seen by clang (and clang-static-analyzer) and changes are explained in the ChangeLog entry. Patch can bootstrap on x86_64-linux-gnu and survives regression tests. Ready to be installed? Thanks, Martin gcc/ChangeLog: 2019-08-26 Martin Liska *

[Patch][PR91504] Inlining misses some logical operation folding

2019-08-26 Kamlesh Kumar * gcc/match.pd: Added simplification pattern. * gcc.dg/tree-ssa/pr91504.c: New test. diff --git a/gcc/match.pd b/gcc/match.pd index 93dcef9..b3734f8 100644 --- a/gcc/match.pd +++ b/gcc/match.pd @@ -831,6 +831,11 @@