On Fri, 2020-01-24 at 19:53 -0500, David Malcolm wrote:
> This patch fixes various build failures seen with gcc 4.4
>
> gcc prior to 4.6 complains about:
>
> error: #pragma GCC diagnostic not allowed inside functions
>
> for various uses of PUSH_IGNORE_WFORMAT and POP_IGNORE_WFORMAT.
> This pa
On Sat, 2020-01-25 at 15:14 +0100, Hans-Peter Nilsson wrote:
> Compared to the cc0 version, I noticed a regression in
> delay-slot-filling for CRIS for several functions in libgcc with
> a similar layout, one being lshrdi3, where with cc0 all
> delay-slots were filled, as exposed by the test-case.
On Fri, 2020-01-17 at 12:07 +, Richard Sandiford wrote:
> PR91323 was fixed for x86 and sparc in target code, but aarch64
> instead relies on the target-independent comparison splitters.
> Since LTGT is an unordered-signalling operation, we should split
> it into unordered-signalling operations
On Mon, 2020-01-20 at 12:54 +, Richard Sandiford wrote:
> g:3bd2918594dae34ae84f mishandled the case in which only the
> tail end of a multireg hard register is invalidated by the call.
> Walking all the entries should be both safer and more precise.
>
> Avoiding cselib_invalidate_regno also m
On Mon, 2020-01-20 at 13:03 +, Richard Sandiford wrote:
> lra_assign has an assert to make sure that no pseudo is allocated
> to a conflicting hard register. It used to be restricted to
> !flag_ipa_ra, but in g:a1e6ee38e708ef2bdef4 I'd enabled it for
> flag_ipa_ra too. It then tripped while b
On Sat, 2020-01-25 at 23:21 -0500, Jason Merrill wrote:
> Here, we end up calling gen_type_die_with_usage for a type that's in the
> middle of finish_struct_1, after we set TYPE_NEEDS_CONSTRUCTING on it but
> before we copy all the flags to the variants--and, significantly, before we
> set its TYPE
On Tue, 2020-01-21 at 14:18 +0200, Darius Galis wrote:
> Hello,
>
> The following patch updates the setmemsi and rx_setmem functions.
> The patch adds the rx_allow_string_insns constraint to these functions
> in order to be used only when the string support is enabled.
>
> Regression test is OK,
On Tue, 2020-01-21 at 02:19 +, Maciej W. Rozycki wrote:
> On Fri, 20 Dec 2019, Mike Stump wrote:
>
> > > > This patch series addresses a problem with the testsuite compiler being
> > > > set up across libatomic, libffi, libgo, libgomp with no correlation
> > > > whatsoever to the target comp
On Tue, 2020-01-21 at 13:48 +0100, Martin Liška wrote:
> From a3faaced989869867671ceadd89b56fabde225ff Mon Sep 17 00:00:00 2001
> From: Martin Liska
> Date: Thu, 16 Jan 2020 10:38:41 +0100
> Subject: [PATCH] Make target_clones resolver fn static.
>
> gcc/ChangeLog:
>
> 2020-01-17 Martin Liska
On Mon, 2020-01-27 at 04:53 +, Feng Xue OS wrote:
> Current IPA does not propagate aggregate constant for by-ref argument
> if it is simple pass-through of caller parameter. Here is an example,
>
>f1 (int *p)
>{
> ... = *p;
> ...
>}
>
>f2 (int *p)
>{
> *p =
On Mon, 2020-01-27 at 16:41 +, Richard Sandiford wrote:
> In the gcc.target/aarch64/lsl_asr_sbfiz.c part of this PR, we have:
>
> Failed to match this instruction:
> (set (reg:SI 95)
> (ashift:SI (subreg:SI (sign_extract:DI (subreg:DI (reg:SI 97) 0)
> (const_int 3 [0x3])
>
On Mon, 2020-01-27 at 17:02 +, Richard Sandiford wrote:
> gcc.dg/pr56350.c started ICEing for SVE in GCC 10 because we
> pattern-matched a division reduction:
>
> a /= 8;
>
> into a signed shift with division semantics:
>
> ... = IFN_SDIV_POW2 (..., 3);
>
> whereas the reduction
On Mon, 2020-01-27 at 15:01 +0100, Hans-Peter Nilsson wrote:
> > From: Jeff Law
> > Date: Fri, 20 Sep 2019 17:38:38 +0200
>
> Hi. I'm not going to question
>
> > The first step in that process is to drop support for cc0.
>
> but could you please elaborate
On Mon, 2019-12-16 at 11:18 +, Bader, Lucas wrote:
> Hello,
>
> within a compile cluster, only the preprocessed output of GCC is transferred
> to remote nodes for compilation.
> When GCC produces advanced diagnostics (with -fdiagnostics-show-caret), e.g.
> prints out the affected source
> l
On Thu, 2019-12-12 at 15:44 -0500, Jason Merrill wrote:
> Here are the dumps from ssa-dom-thread-7.c made to compile as C++; cx-current
> is the dumps with current trunk; cx-old is changed to use the old goto-based
> lowering like C.
Sorry this has taken so long to get back to.
For ssa-dom-threa
On Mon, 2020-01-27 at 18:23 +, Joseph Myers wrote:
> mips_declare_object_name is missing the support for declaring symbols
> as gnu_unique_object that is present in the generic
> ASM_DECLARE_OBJECT_NAME in elfos.h. I'm not aware of any
> MIPS-specific reason for that support to be absent;
> mi
On Tue, 2020-01-28 at 00:33 +0100, Jakub Jelinek wrote:
> Hi!
>
> libgcrypt FAILs to build on aarch64-linux with
> *** stack smashing detected ***: terminated
> when gcc is compiled with -D_FORTIFY_SOURCE=2. The problem is if
> fold_array_ctor_reference is called with size equal to or very close
On Mon, 2020-01-27 at 22:32 +, Andrew Burgess wrote:
> I know that the tree's currently closed to non-bugfix changes, but I
> was hoping this might be accpeted anyway so it can be backported to
> binutils-gdb.
>
> ---
>
> Makes some parameters const in libiberty's hashtab library.
>
> includ
On Tue, 2020-01-28 at 00:41 +0100, Jakub Jelinek wrote:
> Hi!
>
> The following testcase is miscompiled, because the variable shift left
> operand, { -1, -1, -1, -1 } is represented as a VECTOR_CST with
> VECTOR_CST_NPATTERNS 1 and VECTOR_CST_NELTS_PER_PATTERN 1, so when
> we call builder.new_unar
On Tue, 2019-10-08 at 18:04 +0300, Alexander Monakov wrote:
> On Thu, 3 Oct 2019, Jeff Law wrote:
>
> > You may want to review the 2018 discussion:
> >
> > https://www.mail-archive.com/gcc-patches@gcc.gnu.org/msg185287.html
> >
> > THe 2018 discussion was pri
On Thu, 2019-10-17 at 16:14 +0300, Alexander Monakov wrote:
> On Tue, 8 Oct 2019, Alexander Monakov wrote:
>
> [massive snip]
>
> > So in my opinion our CFG is good enough, the real issues with -Wclobbered
> > false
> > positives are not due to phi nodes but other effects.
> >
> > If you agree:
BUILT_IN_OBJECT_SIZE))
+ && ref_maybe_used_by_stmt_p (use_stmt, ref))
{
/* Handle common cases where we can easily build an ao_ref
structure for USE_STMT and in doing so we find that the
commit f4e5d3f4755b6a5846ac20b53008b90131a8bb7c
Author: Jeff
jects.
>
> So OK for P2.
Here's the patch I committed for the historical record. It just adds
the test and ChangeLog entries relative to the RFA/RFC originally
posted.
Jeff
commit 786083766459723b790405c9ba22f974f84f637e
Author: Jeff Law
Date: Wed Jan 29 12:23:53 2020 -0700
Joseph, you were the last one in this part of
c_parser_switch_statement, but the change you made was for supporting
atomics. I'm not sure if you'll have context here or not.
PR88660 is a false positive warning for a set-but-unused object. We
can see trivially from the testcase that "i" is used
'm also watching for other targets that may
need similar handling as a result of the SRA work.
Jeff
diff --git a/gcc/testsuite/ChangeLog b/gcc/testsuite/ChangeLog
index 0247d2cd083..269adb29e94 100644
--- a/gcc/testsuite/ChangeLog
+++ b/gcc/testsuite/ChangeLog
@@ -1,3 +1,8 @@
+2020-01-30 Jeff L
On Wed, 2020-01-29 at 19:18 +, Richard Sandiford wrote:
> Andreas Schwab writes:
> > On Jan 27 2020, Richard Sandiford wrote:
> >
> > > * simplify-rtx.c (simplify_truncation): Extend sign/zero_extract
> > > simplification to handle subregs as well as bare regs.
> >
> > That breaks gcc.ta
On Thu, 2020-01-30 at 18:27 +0100, Jakub Jelinek wrote:
> On Thu, Jan 30, 2020 at 10:23:35AM -0700, Jeff Law wrote:
> > diff --git a/gcc/config/m68k/m68k.md b/gcc/config/m68k/m68k.md
> > index 8e35357ea23..78c4cbe4753 100644
> > --- a/gcc/config/m68k/m68k.md
> > ++
On Thu, 2020-01-30 at 17:54 +, Richard Sandiford wrote:
> Jeff Law writes:
> > On Wed, 2020-01-29 at 19:18 +, Richard Sandiford wrote:
> > > Andreas Schwab writes:
> > > > On Jan 27 2020, Richard Sandiford wrote:
> > > >
> > > >
On Mon, 2020-02-03 at 10:04 -0600, Pat Haugen wrote:
> On 2/3/20 2:17 AM, Jiufu Guo wrote:
> > +/* { dg-final { scan-rtl-dump-times "REG_BR_PROB 937042044" 1
> > "loop2_unroll"} } */
>
> Sorry I didn't catch this addition to the original testcase earlier, but I
> wonder how stable this test is g
On Mon, 2020-02-03 at 12:38 +0100, Claudiu Zissulescu wrote:
> TARGET_INSN_COST gives us a better control over the instruction costs
> than classical RTX_COSTS. A simple cost scheme is in place for the
> time being, when optimizing for size, the cost is given by the
> instruction length. When opti
On Mon, 2020-02-03 at 12:38 +0100, Claudiu Zissulescu wrote:
> This option was used to control the short instruction selection. However,
> there is no difference in cycles if we use or not a short instruction,
> and always someone wants a smaller program.
>
> gcc/
> -xx-xx Claudiu Zissulescu
On Mon, 2020-02-03 at 12:38 +0100, Claudiu Zissulescu wrote:
> For ARC, predicated instructions are not very friendly with size
> optimizations, leading to increased object size. Disable if-conversion
> step when optimized for size.
>
> gcc/
> -xx-xx Claudiu Zissulescu
>
> * common/c
On Fri, 2020-01-31 at 15:50 -0300, Vitor Guidi wrote:
> I took the required steps. The patch is attached to this email, I hope
> I got it right this time. I did not forward the patch to gcc-patches
> the first time, sorry for the inconvenience.
>
> Thank you for your attention,
>
> Vitor.
>
> in
On Mon, 2020-02-03 at 12:38 +0100, Claudiu Zissulescu wrote:
> The ARC 600 MUL64 instructions are using mlo/mhi registers to pass the
> 64-bit result. However, the mlo/mhi registers are not swapping
> depending on endianess. Update multiplication patterns to reflect
> this fact.
>
> gcc/
> -x
On Fri, 2020-01-31 at 12:04 -0700, Martin Sebor wrote:
> Attached is a reworked patch since the first one didn't go far
> enough to solve the major problems. The new solution relies on
> get_range_strlen_dynamic the same way as the sprintf optimization,
> and does away with the determine_min_objsi
On Tue, 2020-02-04 at 10:34 +0100, Richard Biener wrote:
> On Tue, Feb 4, 2020 at 1:44 AM Martin Sebor wrote:
> > PR 93519 reports a false positive -Wrestrict issued for an inlined call
> > to strcpy that carefully guards against self-copying. This is caused
> > by the caller's arguments substitu
On Tue, 2020-02-04 at 13:08 -0700, Martin Sebor wrote:
> On 2/4/20 12:15 PM, Richard Biener wrote:
> > On February 4, 2020 5:30:42 PM GMT+01:00, Jeff Law wrote:
> > > On Tue, 2020-02-04 at 10:34 +0100, Richard Biener wrote:
> > > > On Tue, Feb 4, 2020 at 1:44 AM Mar
case in 90275, but I'm confident this is ultimately all the same
problem.
OK for the trunk?
Thanks,
Jeff
diff --git a/gcc/ChangeLog b/gcc/ChangeLog
index d6b5ded32a4..90d9f9d92d3 100644
--- a/gcc/ChangeLog
+++ b/gcc/ChangeLog
@@ -1,3 +1,8 @@
+2020-02-04 Jeff Law
+
+ PR rtl-optimizati
On Wed, 2020-02-05 at 09:19 +0100, Richard Biener wrote:
> On Tue, Feb 4, 2020 at 11:02 PM Martin Sebor wrote:
> > On 2/4/20 2:31 PM, Jeff Law wrote:
> > > On Tue, 2020-02-04 at 13:08 -0700, Martin Sebor wrote:
> > > > On 2/4/20 12:15 PM, Richard Biener wrote:
>
On Wed, 2020-02-05 at 16:57 -0700, Martin Sebor wrote:
>
> It passes thanks to the TREE_CODE (arg) == PARM_DECL test added
> in the patch to get_range_strlen (the test was missing before
> and so while it handled ordinary objects (local or global) it
> unnecessarily excluded function arguments.
Oh
On Wed, 2020-02-05 at 13:30 +, Richard Sandiford wrote:
> Jeff Law writes:
> > Richard & Segher, if y'all could check my analysis here, it'd be
> > appreciated.
> >
> > pr90275 is a P2 regression that is only triggering on ARM. David's
> >
of shadd insns.
Committed to the trunk.
Jeff
commit f976fe0937c2b46880628c2e2749ca3a788c5db0
Author: Jeff Law
Date: Wed Feb 5 10:00:48 2020 -0700
Fix testsuite "regression" on hppa after recent IRA changes.
* gcc.target/hppa/shadd-3.c: Disable delay slot filling and
On Thu, 2020-02-06 at 07:56 -0600, Segher Boessenkool wrote:
> On Wed, Feb 05, 2020 at 11:48:23AM -0700, Jeff Law wrote:
> > Yea, it's closely related. In your case you need to effectively ignore
> > the nop insn to get the optimization you want. In mine that nop in
On Thu, 2020-02-06 at 14:16 +0100, Richard Biener wrote:
> On Thu, Feb 6, 2020 at 2:00 PM Jeff Law wrote:
> > On Wed, 2020-02-05 at 09:19 +0100, Richard Biener wrote:
> > > On Tue, Feb 4, 2020 at 11:02 PM Martin Sebor wrote:
> > > > On 2/4/20 2:31 PM, Jeff Law wrote
libgcc to avoid the error.
I've verified this fixes the libgcc build failure for FRV and verified
that the GCC testresults have returned to normal.
Installed on the trunk,
Jeff
commit 7214fce3024d726ad548d7003fa162eb5021c491
Author: Jeff Law
Date: Mon Feb 10 14:12:32 2020 -0700
Fix l
On Tue, 2020-02-11 at 16:01 -0700, Martin Sebor wrote:
> Along with some special handling of calloc calls, r272717 introduced
> the assumption into stmt_kills_ref_p that the value returned from
> the call is used. The code triggers an ICE when invoked during DCE
> in an attempt to determine whethe
in particular is useful to simplify the cc0
conversion.
Installing on the trunk momentarily.
Jeff
commit e5cc04a73a3e212114ca9725911eaaa66d32303c
Author: Jeff Law
Date: Wed Feb 12 10:35:12 2020 -0700
Clean up dead patterns, splitters, expanders and peepholes on the H8 port.
On Tue, 2020-02-11 at 15:54 +0100, Hans-Peter Nilsson wrote:
> I was using ira-conflicts.c:print_hard_reg_set with a local
> patch to gdbinit.in in a debug-session, and noticed the
> erroneous output. I see there's an almost identical function in
> ira-color.c and on top of that, there's another f
On Mon, 2020-02-10 at 15:47 -0700, Martin Sebor wrote:
> The reporter of RHBZ #1798636 was mislead and confused by GCC
> issuing -Wstringop-truncation for a possible overflow in strncat.
> It took a few iterations to appreciate this subtlety and realize
> the warning was of the wrong kind.
>
> The
when fed
by a simple (and) operation were consolidated into a single peephole2.
These are still triggering which may point to a failing of the match.pd
patterns, but addressing in match.pd seems terribly out of scope at
this point.
Installing on the trunk.
Jeff
commit 37462a131c528d0980915d98567361a
On Mon, 2020-02-10 at 10:24 +0100, Jakub Jelinek wrote:
> Hi!
>
> I'd like to ping a couple of patches:
>
> PR target/91913 - arm movsi + cmpsi -> movsi_compare0 peephole2 ICE fix
>https://gcc.gnu.org/ml/gcc-patches/2020-02/msg00010.html
Letting the ARM guys deal with this.
>
> PR preproce
On Thu, 2020-02-06 at 14:05 +0100, Mihailo Stojanovic wrote:
> Unnecessary moves around dpadd and dpsub are caused by different pseudos
> being assigned to the input-output operands which correspond to the same
> register.
>
> Just like for the MSA multiply-accumulate instructions, this forces the
hortening peepholes): Use
a mode iterator to merge the HImode and SImode peepholes.
diff --git a/gcc/ChangeLog b/gcc/ChangeLog
index b566ca4b591..fe42cee9e22 100644
--- a/gcc/ChangeLog
+++ b/gcc/ChangeLog
@@ -1,3 +1,8 @@
+2020-02-12 Jeff Law
+
+ * config/h8300/h8300.md (c
On Thu, 2020-02-13 at 00:30 -0500, Mike Frysinger wrote:
> We use this in the sim tree currently. Rather than require people to
> have pkg-config installed, include it in the config/ dir.
>
> 2012-12-23 Mike Frysinger
>
> * pkg.m4: New file from pkg-config-0.29.2.
Presumably you're send
On Thu, 2020-02-13 at 00:27 -0500, Mike Frysinger wrote:
> SVN r216772 accidentally copied & pasted this prototype when adding
> other ones nearby.
>
> 2020-02-13 Mike Frysinger
>
> * libiberty.h (strverscmp): Delete duplicate prototype.
OK. Please push if you've got privs. If not, let
On Thu, 2020-02-13 at 01:30 -0300, Alexandre Oliva wrote:
> vxworks7 headers haven't required fixes, and we've long avoided
> running fixinc on them.
>
> The problem with that is that, with a dummy fixinc, mkheaders wipes
> out include-fixed but then multi_dir subdirs are not created again, so
> w
On Mon, 2020-02-10 at 14:33 +0100, Mihailo Stojanovic wrote:
> Similar to the mirror case of allocating an FPR for an integer mode
> pseudo, prevent GPRs from being allocated for a floating mode pseudo.
>
> gcc/ChangeLog:
>
> * gcc/config/mips/mips.c (mips_ira_change_pseudo_allocno_class)
On Thu, 2020-02-13 at 18:57 +0100, Jakub Jelinek wrote:
> Hi!
>
> The following testcase ICEs, because the PR84305 changes try to evaluate
> the size earlier. If size has side-effects, that is desirable, and the
> side-effects will actually be wrapped in a SAVE_EXPR. The problem on this
> testca
On Thu, 2020-02-13 at 10:42 -0700, Martin Sebor wrote:
> On 2/13/20 2:54 AM, Jakub Jelinek wrote:
> > On Wed, Feb 12, 2020 at 02:39:05PM -0700, Jeff Law wrote:
> > > On Mon, 2020-02-10 at 10:24 +0100, Jakub Jelinek wrote:
> > > > Hi!
> > > >
&g
On Thu, 2020-02-06 at 04:07 -0300, Alexandre Oliva wrote:
> Thread-local variables with DECL_COMMON trigger an internal compiler
> error on targets that use emulated TLS without register_common, when
> we attempt to expand a call to the NULL register_common, with
> testcases as simple as gcc.dg/tls
On 12/4/19 8:24 AM, Wilco Dijkstra wrote:
> Hi Jeff,
>
>>> I've noticed quite significant package failures caused by the revision.
>>> Would you please consider documenting this change in porting_to.html
>>> (and in changes.html) for GCC 10 release?
>>
>> I'm not in the office right now, but figur
On 12/4/19 2:03 PM, Joseph Myers wrote:
> On Wed, 4 Dec 2019, Jeff Law wrote:
>
>>> So what normally happens with the numerous new warnings/errors in GCC
>>> releases? I suppose that could cause package failures too. Would it be
>>> feasible
>>> to ove
On 12/5/19 2:16 AM, Martin Liška wrote:
>
>>
>> Of the ~450 packages affected I'd estimate that even with the opt-out
>> mechanism we're still going to have to fix ~100 packages immediately
>> because they don't honor the flags injection mechanisms which the
>> opt-out approach relies upon.
>
> F
On 12/5/19 4:32 AM, Jozef Lawrynowicz wrote:
> MSP430 RTL patterns for conditional branch instructions allow the post
> increment addressing mode to be used for the "dest" operand of CMP
> instructions
> used in these patterns.
>
> This is currently causing trunk to FTB for msp430-elf since these
On 12/5/19 9:24 AM, Paul Koning wrote:
>
>
>> On Dec 5, 2019, at 11:17 AM, Joseph Myers
>> wrote:
>>
>> On Thu, 5 Dec 2019, Thomas Schwinge wrote:
>>
>>> In the relevant session at the GNU Tools Cauldron 2019, Michael
>>> Meissner stated that even he is not using a 80 x 24 terminal
>>> anymore
On 12/5/19 6:18 AM, Wilco Dijkstra wrote:
> Hi,
>
> I have updated the documentation patch here and added relevant maintainers
> so hopefully this can go in soon:
> https://gcc.gnu.org/ml/gcc-patches/2019-12/msg00311.html
>
> I moved the paragraph in changes.html to the C section like you sugges
On Thu, 2019-12-05 at 15:22 -0700, Martin Sebor wrote:
> PR middle-end/92622 - FAIL: gcc.dg/Warray-bounds-22.c on ILP32:
> missing warnings for VLA on lines 67 and 69
>
> gcc/ChangeLog:
>
> PR testsuite/92622
> * tree-vrp.c (vrp_prop::check_array_ref): Avoid using a
> variable
>
On Fri, 2019-12-06 at 10:17 +, Richard Sandiford wrote:
> While trying out Dennis's Armv8.6-A patch, I noticed that texi2pod.pl
> didn't handle the new @multitable correctly. There were two
> problems:
>
> (1) @multitables nested in other @tables inherited the @item type
> from
> the encl
On Thu, 2019-12-05 at 11:12 +0100, Jan Hubicka wrote:
> Hi,
> this patch makes tree-ssa-threadupdate to not leave basic blocks with
> undefined counts in the program.
>
> create_block_for_threading sets counts as follows:
>
> /* Zero out the profile, since the block is unreachable for
> now.
On Thu, 2019-11-28 at 22:10 +0100, Tim Rühsen wrote:
> An empty name param leads to read buffer overflow in
> function split_directories.
>
> * libiberty/make-relative-prefix.c (split_directories):
> Return early on empty name.
> ---
> libiberty/ChangeLog | 7 +++
> libiberty/m
On Tue, 2019-12-03 at 11:52 -0500, David Malcolm wrote:
> On Wed, 2019-11-20 at 11:18 +0100, Richard Biener wrote:
> > On Tue, Nov 19, 2019 at 11:02 PM David Malcolm > >
> > wrote:
> > > > > The checker is implemented as a GCC plugin.
> > > > >
> > > > > The patch kit adds support for "in-tree" p
On Wed, 2019-12-04 at 12:55 -0700, Martin Sebor wrote:
> On 11/15/19 6:22 PM, David Malcolm wrote:
> > This patch kit introduces a static analysis pass for GCC that can
> > diagnose
> > various kinds of problems in C code at compile-time (e.g. double-
> > free,
> > use-after-free, etc).
>
> I have
On Wed, 2019-11-13 at 09:27 -0700, Sandra Loosemore wrote:
>
> I bootstrapped and regression-tested this on x86_64-linux-gnu. There
> are a few regressions involving these tests:
>
> gcc.dg/tree-ssa/pr77445-2.c
I believe tihs is another instance of the FSA optimization. I'd need
to see the befo
On Tue, 2019-11-12 at 09:11 +, Matthew Malcomson wrote:
> In scheduling passes, notes are removed with `remove_notes` before
> the
>
> scheduling is done, and added back in with `reemit_notes` once the
>
> scheduling has been decided.
>
>
>
> This process leaves the notes in the RTL chain
On Fri, 2019-11-15 at 20:22 -0500, David Malcolm wrote:
> This patch converts various "gimple *" to "const gimple *" and
> similar
> fixes for gimple subclasses, adding is_a_helper for gimple subclasses
> to support the const form of as_a, and adding a few "const" overloads
> of accessors.
>
> Thi
On Fri, 2019-11-15 at 20:22 -0500, David Malcolm wrote:
> This patch adds a class "auto_client_timevar", similar to
> auto_timevar,
> but for plugins to use on their own timing items that aren't in
> timevar.def
>
> gcc/ChangeLog:
> * timevar.h (class auto_client_timevar): New class.
So if w
On Fri, 2019-11-15 at 20:22 -0500, David Malcolm wrote:
> diagnostic_show_locus adds a newline before doing anything (including
> the do-nothing-else case).
>
> This patch removes this initial newline, adding it to all callers
> of diagnostic_show_locus instead.
>
> Doing so makes diagnostic_show
On Fri, 2019-11-15 at 20:22 -0500, David Malcolm wrote:
> libcpp's label_text class wraps a text buffer, along with a flag to
> determine if it "owns" the buffer.
>
> The existing ctor exposed this directly, but I found it difficult
> to remember the sense of flag, so this patch hides the ctor, in
On Fri, 2019-11-15 at 20:22 -0500, David Malcolm wrote:
> This patch provides a way to clone a pretty_printer.
>
> This is needed so that we can capture text in a label_text and make
> layout decisions based on it, using the policy of global_dc's
> printer,
> whilst within a call to diagnostic_sho
On Fri, 2019-11-15 at 20:23 -0500, David Malcolm wrote:
> This is used by new selftests later on in the patch kit.
>
> gcc/ChangeLog:
> * function-tests.c (selftest::make_fndecl): Make non-static.
> * selftest.h (selftest::make_fndecl): New decl.
OK
jeff
On Fri, 2019-11-15 at 20:23 -0500, David Malcolm wrote:
> gcc/ChangeLog:
> * hash-map-tests.c (selftest::test_map_of_int_to_strings): New
> selftest.
> (selftest::hash_map_tests_c_tests): Call it.
OK
jeff
>
On Fri, 2019-11-15 at 20:23 -0500, David Malcolm wrote:
> This patch adds support for "in-tree" plugins i.e. GCC plugins that
> live
> in the GCC source tree and are shipped as part of the GCC tarball.
>
> The patch adds Makefile/configure machinery for handling in-tree GCC
> plugins, adapted from
On Fri, 2019-11-15 at 20:23 -0500, David Malcolm wrote:
> This patch provides a plugin callback for invoking selftests, so that
> a
> plugin can add tests to those run by -fself-test=DIR. The callback
> invocation uses invoke_plugin_callbacks, which is a no-op if plugin
> support is disabled.
>
>
On Fri, 2019-11-15 at 20:22 -0500, David Malcolm wrote:
> This patch adds support for associating a "diagnostic_path" with a
> diagnostic: a sequence of events predicted by the compiler that leads
> to
> the problem occurring, with their locations in the user's source,
> text descriptions, and stac
On Fri, 2019-11-15 at 20:23 -0500, David Malcolm wrote:
> gcc/ChangeLog:
> * analyzer/analyzer-selftests.cc: New file.
> * analyzer/analyzer-selftests.h: New file.
This obviously can't stand on its own, but it's fine once prereqs are
approved.
jeff
On Fri, 2019-11-15 at 20:23 -0500, David Malcolm wrote:
> gcc/ChangeLog:
> * params.def (PARAM_ANALYZER_BB_EXPLOSION_FACTOR): New param.
> (PARAM_ANALYZER_MAX_ENODES_PER_PROGRAM_POINT): New param.
> (PARAM_ANALYZER_MAX_RECURSION_DEPTH): New param.
> (PARAM_ANALYZER_MIN_SNODE
On Fri, 2019-11-15 at 20:23 -0500, David Malcolm wrote:
> This patch adds the IPA pass boilerplate for the analyzer.
>
> gcc/ChangeLog:
> * analyzer/analyzer-pass.cc: New file.
Nothing I see controversial here. But obviously will need some
adjustment if we're moving away from using the plug
On Fri, 2019-11-15 at 20:23 -0500, David Malcolm wrote:
> This patch adds a simple wrapper class to make it easier to
> write human-readable .dot files.
>
> gcc/ChangeLog:
> * analyzer/graphviz.cc: New file.
> * analyzer/graphviz.h: New file.
This doesn't seem specific to the analyzer
On Fri, 2019-11-15 at 20:23 -0500, David Malcolm wrote:
> This patch adds template classes for directed graphs, their nodes
> and edges, and for finding the shortest path through such a graph.
>
> gcc/ChangeLog:
> * analyzer/digraph.cc: New file.
> * analyzer/digraph.h: New file.
>
On Fri, 2019-11-15 at 20:23 -0500, David Malcolm wrote:
> gcc/ChangeLog:
> * analyzer/analyzer.cc: New file.
> * analyzer/analyzer.h: New file.
> ---
> gcc/analyzer/analyzer.cc | 125
> ++
> gcc/analyzer/analyzer.h | 126
> ++
On Fri, 2019-11-15 at 20:23 -0500, David Malcolm wrote:
> gcc/ChangeLog:
> * analyzer/tristate.cc: New file.
> * analyzer/tristate.h: New file.
Nothing really concerning here. Seems like a generic facility we'd
like to be able to use elsewhere. Move outside the analyzer?
jeff
On Fri, 2019-11-15 at 20:23 -0500, David Malcolm wrote:
> This patch adds classes used by the analyzer for handling its
> diagnostics
> (queueing them, deduplicating them, precision-of-wording hooks).
>
> gcc/ChangeLog:
> * analyzer/pending-diagnostic.cc: New file.
> * analyzer/pending
On Fri, 2019-11-15 at 20:23 -0500, David Malcolm wrote:
> This patch adds a state machine checker for malloc/free.
>
> gcc/ChangeLog:
> * analyzer/sm-malloc.cc: New file.
FWIW, I could easily see someone using this as a template for other
checkers. It shows several key concepts that I suspe
On Fri, 2019-11-15 at 20:23 -0500, David Malcolm wrote:
> This patch adds a state machine checker for stdio's FILE stream API.
>
> gcc/ChangeLog:
> * analyzer/sm-file.cc: New file.
I note this seems somewhat incomplete -- which is fine given my
recommendation was to focus on the double-free
On Fri, 2019-11-15 at 20:23 -0500, David Malcolm wrote:
> This patch adds a custom state machine checker intended purely for
> DejaGnu
> testing of the sm "machinery".
>
> gcc/ChangeLog:
> * analyzer/sm-pattern-test.cc: New file.
OK when prereqs are all approved.
jeff
On Fri, 2019-11-15 at 20:23 -0500, David Malcolm wrote:
> This patch adds a state machine checker for tracking exposure of
> sensitive data (e.g. writing passwords to log files).
>
> This checker isn't ready for production, and is presented as a
> proof-of-concept of the sm-based approach.
>
> gc
On Fri, 2019-11-15 at 20:23 -0500, David Malcolm wrote:
> This patch adds a state machine checker for tracking "taint",
> where data potentially under an attacker's control is used for
> things like array indices without sanitization (CWE-129).
>
> This checker isn't ready for production, and is p
On Fri, 2019-11-15 at 20:23 -0500, David Malcolm wrote:
> This patch adds an analysis_plan class, which encapsulate decisions
> about
> how the analysis should happen (e.g. the order in which functions
> should
> be traversed).
>
> gcc/ChangeLog:
> * analyzer/analysis-plan.cc: New file.
>
On Tue, 2019-12-03 at 15:41 -0700, Martin Sebor wrote:
> PR middle-end/92761 - hash_table::expand invokes assignment on invalid objects
> PR middle-end/92762 - hash_table::empty_slow invokes assignment on invalid
> objects
> gcc/ChangeLog:
>
> PR middle-end/92761
> PR middle-end/92762
On Tue, 2019-11-26 at 19:33 +, Michael Witten wrote:
> The problem with false positives is correlated with the degree of
> optimization; a lot of people have reported problems at only the
> `-Og' optimization level (even when the code in question is
> embarrassingly correct).
>
> Theref
501 - 600 of 15555 matches
Mail list logo
