On Mon, Aug 24, 2020 at 8:39 PM Giuliano Belinassi via Gcc-patches
wrote:
>
> Ho, Josh.
>
> On 08/24, Josh Triplett wrote:
> > On Sat, Aug 22, 2020 at 06:04:48PM -0300, Giuliano Belinassi wrote:
> > > Hi, Josh
> > >
> > > On 08/21, Josh Triplett wrote:
> > > > On Thu, Aug 20, 2020 at 07:00:13PM -0
The following makes sure to, at early debug generation time, mangle
symbols we eventually end up outputting during late finish.
[LTO] Bootstrapped and tested on x86_64-unknown-linux-gnu, pushed
to trunk sofar.
Richard.
2020-08-24 Richard Biener
PR debug/96690
* dwarf2out.c (r
On Mon, 24 Aug 2020, Jakub Jelinek wrote:
> Hi!
>
> The following testcase is miscompiled, because handle_builtin_string_cmp
> sees a strncmp call with constant last argument 4, where one of the strings
> has an upper bound of 5 bytes (due to it being an array of that size) and
> the other has a
On Mon, 24 Aug 2020, Jakub Jelinek wrote:
> Hi!
>
> Clobbers of MEM_REF with NULL address are just fancy nops, something we just
> ignore and don't emit any code for it (ditto for other clobbers), they just
> mark end of life on something, so we shouldn't infer from those that there
> is some UB.
On Tue, Aug 25, 2020 at 6:05 AM Alexandre Oliva wrote:
>
> On Aug 24, 2020, Jakub Jelinek wrote:
>
> > On Mon, Aug 24, 2020 at 02:56:54PM +0200, Mark Wielaard wrote:
> >> DWARF5 makes it possible to read loclists tables without consulting
> >> the debuginfo tree by introducing a table header. Add
On 24/08/20 23:19 -0300, Alexandre Oliva wrote:
On Aug 24, 2020, Jonathan Wakely wrote:
OK for trunk, thanks.
Given the approval and the lack of significant changes, I'll put this in
unless there are objections in the next 48 hours. Thanks for the review!
Thanks. There's a new FAIL due
On Aug 15, 2020, Nathan Sidwell wrote:
> 'alias' is also now a confusing term, because of the concept of
> object-aliasing.
True, but it's also an established attribute name. It seems thus
desirable to bring the conceptual framework of the alias attribute to
mind through the name of the attrib
Hey Gerald.
I noticed your continual effort to change http:// links to https://.
I've written a simple script that can do that in automatic way.
What do you think about using it?
Martin
#!/usr/bin/env python3
import os
import re
import requests
urls = set()
def check_url(url):
try:
On Aug 15, 2020, Iain Sandoe wrote:
> Alexandre Oliva wrote:
>> I'm pretty sure setting multiple labels at the same address is used
>> and relied on quite often.
> That’s what’s currently disallowed (the assemblers all support .set).
I understand you mean it's disallowed for global labels. I
Hi Richard,
Thank you for your comments.
I've attached updated patch with changes reflecting your comments.
Kind regards,
Przemyslaw
> -Original Message-
> From: Richard Sandiford
> Sent: 19 August 2020 11:32
> To: Przemyslaw Wirkus
> Cc: gcc-patches@gcc.gnu.org; Richard Earnshaw
> ;
Hi,
On Mon, 2020-08-24 at 17:38 -0400, Jason Merrill wrote:
> > This looks incorrect to me, that is a workaround for a real GCC bug.
> >
> > Shouldn't we instead do something like (untested) following patch?
> > I mean, for DWARF < 5 the static data members were using DW_TAG_member,
> > which has
Hi Alex,
On Tue, 2020-08-25 at 01:05 -0300, Alexandre Oliva wrote:
> it would seem to
> make more sense to adopt and promote the proposed extension,
> implemented in =incompat5 in GCC, but it would need some
> implementation work in consumers to at least ignore the extension.
Is that what is desc
Hi Maciej:
I just found the mail thread about div mod with -fnon-call-exceptions,
I think keeping the default LIB2_DIVMOD_EXCEPTION_FLAGS unchanged
should be the best way to go.
Non-call exceptions and libcalls
https://gcc.gnu.org/legacy-ml/gcc/2001-06/msg01108.html
Non-call exceptions and libca
Hi,
On Mon, 2020-08-24 at 14:56 +0200, Mark Wielaard wrote:
> This afternoon there will be a BoF at the virtual Cauldron about
> DWARF5 and beyond.
> https://linuxplumbersconf.org/event/7/contributions/746/
>
> Here are some patches for GCC that I would like to discuss.
> I'll reply to them afte
gcc/ChangeLog:
* cgraphunit.c (process_symver_attribute): Allow multiple
symver attributes for one symbol.
* doc/extend.texi: Document the change.
gcc/testsuite/ChangeLog:
* lib/target-supports-dg.exp: Add dg-require-symver.
* lib/target-supports.exp: Lik
gcc/ChangeLog:
* cgraphunit.c (process_symver_attribute): Remove checks that
are not needed now.
(cgraph_node::assemble_thunks_and_aliases): Change second
argument to decl.
* config/elfos.h (ASM_OUTPUT_SYMVER_DIRECTIVE): Add new
VISIBILITY parameter
Hey.
Since the bintuils release 2.35, we can now support new .symver syntax added in:
https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=6914be53bd662eefd979d0c82d2e20e108c4ee66
Patch survives bootstrap and regression tests.
Thoughts?
Martin
Martin Liska (2):
IPA symver: allow multiple
Hello,
Inside a (mem) RTX, it is canonical to write multiplications by powers
of two using a (mult) [0]. For example, given the following C function:
long f(long *p, long x)
{
return p[x];
}
AArch64 GCC generates the following RTL insn (in final):
(set (reg/i:DI 0 x0)
(mem:DI (plus:DI
Wei Wentao writes:
> Hi,
>
> This patch fix a typo in rtl.def.
Thanks, pushed. Looks like it had gone unnoticed (or at least unfixed)
for almost 30 years. :-)
Richard
>
> Regards!
>
> Weiwt
>
> ---
> gcc/rtl.def | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/gcc/rtl.
This patch adds support for polymorphic variables ("CLASS")
to OpenMP's data-sharing clause FIRSTPRIVATE.
While the patch should be okay, there is more follow-up
work required, but one has to make a start :-)
* PRIVATE – as used in the testcase of the PR is not yet supported,
only FIRSTPRIVATE
xiezhiheng writes:
>> -Original Message-
>> From: Richard Sandiford [mailto:richard.sandif...@arm.com]
>> Sent: Friday, August 21, 2020 5:02 PM
>> To: xiezhiheng
>> Cc: Richard Biener ; gcc-patches@gcc.gnu.org
>> Subject: Re: [PATCH PR94442] [AArch64] Redundant ldp/stp instructions
>> emi
Przemyslaw Wirkus writes:
> @@ -5234,21 +5234,21 @@ (define_insn_and_rewrite "*cond_sub_3_const"
>
> ;; Predicated floating-point subtraction from a constant, merging with an
> ;; independent value.
> -(define_insn_and_rewrite "*cond_sub_any_const"
> +;; The subtraction predicate and the merge
Alexandre Oliva wrote:
On Aug 15, 2020, Iain Sandoe wrote:
Alexandre Oliva wrote:
I'm pretty sure setting multiple labels at the same address is used
and relied on quite often.
That’s what’s currently disallowed (the assemblers all support .set).
I understand you mean it's disallowe
This recomputes RPO after store-motion changes the CFG.
Bootstrapped on x86_64-unknown-linux-gnu, testing in progress.
Richard.
2020-08-25 Richard Biener
PR tree-optimization/96548
PR tree-optimization/96760
* tree-ssa-loop-im.c (tree_ssa_lim): Recompute RPO after
On Mon, Aug 24, 2020 at 12:40 PM H.J. Lu wrote:
>
> On Mon, Aug 24, 2020 at 12:25 PM Uros Bizjak wrote:
> >
> > On Mon, Aug 24, 2020 at 6:17 PM H.J. Lu wrote:
> > >
> > > On Mon, Aug 24, 2020 at 7:55 AM Uros Bizjak wrote:
> > > >
> > > > On Mon, Aug 24, 2020 at 3:23 PM H.J. Lu wrote:
> > > >
>
On Mon, Aug 24, 2020 at 10:49:38PM -0400, Jason Merrill wrote:
> On 8/24/20 5:44 PM, Marek Polacek wrote:
> > --- a/gcc/tree.c
> > +++ b/gcc/tree.c
> > @@ -2123,6 +2123,23 @@ build_constructor_from_list (tree type, tree vals)
> > return build_constructor (type, v);
> > }
> > +/* Return a new
On Tue, Aug 25, 2020 at 2:13 PM H.J. Lu wrote:
>
> On Mon, Aug 24, 2020 at 12:40 PM H.J. Lu wrote:
> >
> > On Mon, Aug 24, 2020 at 12:25 PM Uros Bizjak wrote:
> > >
> > > On Mon, Aug 24, 2020 at 6:17 PM H.J. Lu wrote:
> > > >
> > > > On Mon, Aug 24, 2020 at 7:55 AM Uros Bizjak wrote:
> > > > >
GCC was implementing an old mangling scheme for single SVE
vectors and predicates (based on the Advanced SIMD one).
The final definition instead put them in the vendor built-in
namespace via the "u" prefix.
Tested on aarch64-linux-gnu, aarch64-elf and aarch64_be-elf.
Pushed to trunk so far, will b
This patch is really four things rolled into one, since separating
them seemed artificial:
- Update the mangling of the fixed-length SVE ACLE types to match
the upcoming spec. The idea is to mangle:
VLAT __attribute__((arm_sve_vector_bits(N)))
as an instance __SVE_VLS of the template:
GCC used the name __ARM_FEATURE_SVE_VECTOR_OPERATIONS, but in the
final spec it was renamed to__ARM_FEATURE_SVE_VECTOR_OPERATORS.
Tested on aarch64-linux-gnu, aarch64-elf and aarch64_be-elf.
Pushed to trunk so far, will backport to GCC 10 soon.
Richard
gcc/
* config/aarch64/aarch64-c.c
On Mon, Aug 24, 2020 at 05:38:28PM -0400, Jason Merrill via Gcc-patches wrote:
> > Shouldn't we instead do something like (untested) following patch?
> > I mean, for DWARF < 5 the static data members were using DW_TAG_member,
> > which has been always marked by the function, so IMHO we should also
Hi Bin,
>>
>> For one particular case like:
>>
>> for (i = 0; i < SIZE; i++)
>> y[i] = a * x[i] + z[i];
>>
>> we will mark reg_offset_p for IV candidates on x as below:
>>- (unsigned long) (x_18(D) + 8)// only mark this before.
>>- x_18(D) + 8
>>- (unsigne
OG10 = devel/omp/gcc-10
* Merged GCC 10 into branch
commit 68294a5e478a3215763530ae71dc0da4a0a9aa20
OpenMP/Fortran: Reject allocatable components in map clause
(cherry picked from commit ac70b20b1007da0d3d02a9cec3c0715145c4b593)
commit 575f1eb0711550adce9c61c04ff5597d71a1cc5c
OpenMP:
On 24/08/20 23:01 -0400, Patrick Palka via Libstdc++ wrote:
This patch adds the C++20 calendar types and their methods as defined in
[time.cal] (modulo the parsing/printing support). This patch also
implements [time.hms] and [time.12], and a few more bits of
[time.clock]. The remaining C++20 ad
> On Aug 25, 2020, at 1:41 AM, Uros Bizjak wrote:
>
>>>
> (The other side of the coin is how much this helps prevent exploitation;
> numbers on that would be good to see, too.)
This can be well showed from the paper:
"Clean the Scratch Registers: A Way to Mitigat
On Sat, 2020-08-22 at 09:52 +0100, Roger Sayle wrote:
> Hi Dave,
>
> It's great to hear from you. It's been a long while.
>
> Sorry, doh! yes, there's a mistake in my patch (that I introduced when I
> renumbered
> the operands in the shd's define_expand to be the more logical 0, 1, 2, 3,
> then
On Tue, 2020-08-25 at 02:16 -0300, Alexandre Oliva wrote:
> On Aug 24, 2020, Richard Biener wrote:
>
> > since the option is quite elaborate on what (sub-)set of regs is
> > supposed to be cleared I'm not sure an implementation not involving
> > any target hook is possible?
>
> I don't think thi
On 17/08/20 19:13 +0200, François Dumont via Libstdc++ wrote:
Hi
   Here is the new proposal.
   As we can't remove template parameters I simply restore those that
I tried to pass differently _H2 and _ExtractKey, so eventually I only
remove usage of _Hash which I renamed in _Unused.
On 2020-08-25 10:05 a.m., Jeff Law wrote:
> On Sat, 2020-08-22 at 09:52 +0100, Roger Sayle wrote:
>> Hi Dave,
>>
>> It's great to hear from you. It's been a long while.
>>
>> Sorry, doh! yes, there's a mistake in my patch (that I introduced when I
>> renumbered
>> the operands in the shd's define_
On 2020-08-21 2:41 p.m., Roger Sayle wrote:
> 2020-08-21 Roger Sayle
>
> gcc/ChangeLog
> PR middle-end/87256
> * config/pa/pa.c (hppa_rtx_costs_shadd_p): New helper function
> to check for coefficients supported by shNadd and shladd,l.
> (hppa_rtx_costs): Rewrite to avoi
This would solve a common pattern in the kernel where folks are using
`extern inline` with `gnu_inline` semantics or worse (empty `asm("");`
statements) in certain places where it would be much more preferable
to have this attribute. Thank you very much Martin for writing it.
> is direct equivale
Add a static_assertions to check the result type is destructible, as in
the proposed resolution for LWG 3466 (which supersedes 3458).
libstdc++-v3/ChangeLog:
* include/std/future (future, shared_future. promise): Add
is_destructible assertion (LWG 3466). Adjust string-literal for
libstdc++-v3/ChangeLog:
* include/std/chrono (year_month_weekday::ok): Fix assert.
---
libstdc++-v3/include/std/chrono | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/libstdc++-v3/include/std/chrono b/libstdc++-v3/include/std/chrono
index bf0d7e7af76..3cc1438a7b6 10064
Improve the error message. Currently code like:
void test (double src[100])
{
#pragma omp target map(alloc:src[:])
fails with the surprising
"for pointer type length expression must be specified"
as "double src[100]" is regarded as "double *src".
Thus, one cannot simply extract the "100" and
On Tue, Aug 25, 2020 at 05:33:08PM +0200, Tobias Burnus wrote:
> Improve the error message. Currently code like:
>
> void test (double src[100])
> {
> #pragma omp target map(alloc:src[:])
>
> fails with the surprising
> "for pointer type length expression must be specified"
> as "double src[10
On 12/08/20 20:37 +0100, Jonathan Wakely wrote:
The C++ LWG recently confirmed that self-move assignment should not have
undefined behaviour for standard containers (see the proposed resolution
of LWG 2839). The result should be a valid but unspecified value, just
like other times when a containe
Hi Kito,
> I just found the mail thread about div mod with -fnon-call-exceptions,
> I think keeping the default LIB2_DIVMOD_EXCEPTION_FLAGS unchanged
> should be the best way to go.
>
> Non-call exceptions and libcalls
> https://gcc.gnu.org/legacy-ml/gcc/2001-06/msg01108.html
>
> Non-call except
On Mon, 2020-08-24 at 14:39 -0700, Carl Love wrote:
> Segher:
>
> On Wed, 2020-08-19 at 15:16 -0500, Segher Boessenkool wrote:
> > On Wed, Aug 19, 2020 at 02:19:12PM -0500, Peter Bergner wrote:
> > > On 8/14/20 7:42 PM, Segher Boessenkool wrote:
> > > > I think your current code is fine; I hadn't
And another PING.
On 8/17/20 9:17 AM, Tobias Burnus wrote:
On 8/3/20 5:37 PM, Tobias Burnus wrote:
It turned out that the omp_discover_declare_target_tgt_fn_r
discovered all nodes – but as it tagged the C++ alias nodes
and not the streamed-out nodes, no device function was created
and one got l
Joseph, do you have any more comments on the rest of the most recent
revision of the patch?
https://gcc.gnu.org/pipermail/gcc-patches/2020-August/552266.html
Martin
On 8/19/20 6:09 PM, Joseph Myers wrote:
On Wed, 19 Aug 2020, Martin Sebor via Gcc-patches wrote:
I think you need a while loop
>
> gcc/ChangeLog:
>
> * cgraphunit.c (process_symver_attribute): Remove checks that
> are not needed now.
> (cgraph_node::assemble_thunks_and_aliases): Change second
> argument to decl.
> * config/elfos.h (ASM_OUTPUT_SYMVER_DIRECTIVE): Add new
> VISIBILITY par
>
> gcc/ChangeLog:
>
> * cgraphunit.c (process_symver_attribute): Allow multiple
> symver attributes for one symbol.
> * doc/extend.texi: Document the change.
>
> gcc/testsuite/ChangeLog:
>
> * lib/target-supports-dg.exp: Add dg-require-symver.
> * lib/target-suppo
On Mon, 2020-07-13 at 06:42 -0700, H.J. Lu via Gcc-patches wrote:
> Change CTZ_DEFINED_VALUE_AT_ZERO/CTZ_DEFINED_VALUE_AT_ZERO to return 0/2
> to enable table-based clz/ctz optimization:
>
> -- Macro: CLZ_DEFINED_VALUE_AT_ZERO (MODE, VALUE)
> -- Macro: CTZ_DEFINED_VALUE_AT_ZERO (MODE, VALUE)
>
On Tue, 2020-07-21 at 19:29 +0100, Jozef Lawrynowicz wrote:
> The implementation of define_expand and define_insn patterns to handle
> shifts in the MSP430 backend is inconsistent, resulting in missed
> opportunities to make best use of the architecture's features.
>
> There's now a single define_
On Thu, 2020-07-30 at 11:23 +0100, Jonathan Wakely via Gcc-patches wrote:
> I recently wanted to use { dg-require-effective-target fenv } in a
> libstdc++ test, but it uses -std=gnu99 which is only valid for C.
>
> This allows C++ tests to use the fenv and fenv_exceptions
> effective-target keywor
On Sat, 2020-08-01 at 13:38 +0200, Václav Haisman via Gcc-patches wrote:
> On 01. 08. 20 13:02, Jojo R wrote:
> > gcc/ChangeLog:
> >
> > * genemit.c (main): Print 'split line'.
> > * Makefile.in (insn-emit.c): Define split count and file
> >
> > ---
> > gcc/Makefile.in | 11 +++
> >
On Mon, 2020-08-03 at 14:47 -0400, Asher Gordon via Gcc-patches wrote:
> Hello,
>
> Asher Gordon writes:
>
> > My copyright assignment finally got finished, so you should be able to
> > apply my patches now.
>
> Is there any reason my patches haven't been applied yet? Is there
> anything else I
On Wed, Aug 19, 2020 at 1:02 AM Joshua via Gcc-patches
wrote:
> * config/riscv/riscv.c (asan_shadow_offset): Implement the offset of
> asan shadow memory for risc-v.
> (asan_shadow_offset): new macro definition.
When I try the patch, I get asan errors complaining about memory map
On Sun, 2020-08-16 at 06:17 -0700, H.J. Lu via Gcc-patches wrote:
> From arch/x86/include/asm/intel-family.h on Linux kernel master branch:
>
> #define INTEL_FAM6_ROCKETLAKE 0xA7
> #define INTEL_FAM6_ALDERLAKE0x97
>
> * common/config/i386/cpuinfo.h (get_intel_cpu): D
On Tue, 2020-08-18 at 15:18 +0800, Hongtao Liu via Gcc-patches wrote:
> Hi:
> Rewriting testcase with cpp source file, then compare operator could
> be used directly for vector, this would avoid impact of vectorizer.
>
> gcc/testsuite/ChangeLog:
> PR target/96667
> * gcc.target/i
My original patch that implemented the calendar type operations failed
to enforce a constraint on some of the addition/subtraction operator
overloads that take a 'months' argument:
Constraints: If the argument supplied by the caller for the months
parameter is convertible to years, its implici
On Tue, 2020-08-18 at 16:05 +0300, Darius Galis wrote:
> Hello,
>
> The following patch is adding the PC control register.
> It also updates the __builtin_rx_mvfc() function, since
> according to the documentation, the PC register cannot be specified
> as dest.
>
> The regression was tested with
On Tue, 25 Aug 2020, Patrick Palka wrote:
> My original patch that implemented the calendar type operations failed
> to enforce a constraint on some of the addition/subtraction operator
> overloads that take a 'months' argument:
>
> Constraints: If the argument supplied by the caller for the mo
On Tue, Aug 25, 2020 at 01:45:01PM -0600, Jeff Law via Gcc-patches wrote:
> On Tue, 2020-08-18 at 15:18 +0800, Hongtao Liu via Gcc-patches wrote:
> > Hi:
> > Rewriting testcase with cpp source file, then compare operator could
> > be used directly for vector, this would avoid impact of vectorizer
On Tue, 2020-08-25 at 22:01 +0200, Jakub Jelinek wrote:
> On Tue, Aug 25, 2020 at 01:45:01PM -0600, Jeff Law via Gcc-patches wrote:
> > On Tue, 2020-08-18 at 15:18 +0800, Hongtao Liu via Gcc-patches wrote:
> > > Hi:
> > > Rewriting testcase with cpp source file, then compare operator could
> > >
On Fri, 2020-08-21 at 14:18 +0800, Jojo R wrote:
> gcc/ChangeLog:
>
> * config/csky/csky.opt (TARGET_BACKTRACE): New.
> * doc/invoke.texi (C-SKY Options): Document -mbacktrace.
ISTM you need an actual implementation. All this does is add an option. It's
impossible to know if this is
Hi Jeff,
Jeff Law writes:
> On Mon, 2020-08-03 at 14:47 -0400, Asher Gordon via Gcc-patches wrote:
>> Is there any reason my patches haven't been applied yet? Is there
>> anything else I need to do?
> No, nothing you really need to do. We're backed up more than usual, but
> yours is
> definite
On Mon, 2020-08-10 at 11:11 -0500, Peter Bergner wrote:
> On 7/23/20 3:29 PM, Jeff Law wrote:
> > > > What's driving this change?
> > >
> > > Peter noticed IRA allocates stuff to volatile registers while it is life
> > > through a call, and then LRA has to correct that, not optimal.
> > I can't re
On Fri, 2020-08-07 at 21:51 +, Segher Boessenkool wrote:
> When the compgotos pass copies the tail of blocks ending in an indirect
> jump, there is a micro-optimization to not copy the last one, since the
> original block will then just be deleted. This does not work properly
> if cleanup_cfg
On Fri, 2020-08-07 at 13:32 +0200, Iain Buclaw via Gcc-patches wrote:
> Hi,
>
> This patch adds support for 'in' as a first-class storage class with its
> own mangle symbol, of which also permits 'in ref'. Previously, 'in' was
> an alias to 'const [scope]', which is a type constructor.
>
> The m
On 2020-08-25 6:18 a.m., Alex Coplan wrote:
The motivation here is to be able to remove several redundant patterns
in the AArch64 backend. See the previous thread [1] for context.
Testing:
* Bootstrapped and regtested on aarch64-none-linux-gnu,
x86_64-pc-linux-gnu.
* New unit test whic
> On Aug 24, 2020, at 3:20 PM, Segher Boessenkool
> wrote:
>
> Hi!
>
> On Mon, Aug 24, 2020 at 01:02:03PM -0500, Qing Zhao wrote:
>>> On Aug 24, 2020, at 12:49 PM, Segher Boessenkool
>>> wrote:
>>> On Wed, Aug 19, 2020 at 06:27:45PM -0500, Qing Zhao wrote:
> On Aug 19, 2020, at 5:57 PM
> On Aug 25, 2020, at 9:05 AM, Qing Zhao via Gcc-patches
> wrote:
>
>
>
>> On Aug 25, 2020, at 1:41 AM, Uros Bizjak wrote:
>>
>> (The other side of the coin is how much this helps prevent exploitation;
>> numbers on that would be good to see, too.)
>
> This can be w
> -Original Message-
> From: Richard Sandiford [mailto:richard.sandif...@arm.com]
> Sent: Tuesday, August 25, 2020 7:08 PM
> To: xiezhiheng
> Cc: Richard Biener ; gcc-patches@gcc.gnu.org
> Subject: Re: [PATCH PR94442] [AArch64] Redundant ldp/stp instructions
> emitted at -O3
>
> xiezhihen
Successfully bootstrapped & regrtested on x86_64-pc-linux-gnu.
Pushed to master as r11-2854-gd88c8df70342fcd6817e23f243ff38d0fe42fc6b.
gcc/analyzer/ChangeLog:
PR analyzer/96777
* region-model.h (class compound_svalue): Document that all keys
must be concrete.
(compo
PR analyzer/94858 reports a false diagnostic from
-Wanalyzer-malloc-leak, where the allocated pointer is pointed to by a
field of a struct, and a loop writes to a buffer, writing through an
iterating pointer value.
There were several underlying problems, relating to clobbering of the
struct holdin
Hi Maciej:
Thanks for your explanation, I am OK with this change for the RISC-V port now,
but I think I don't have permission to approve this patch since it's
more than RISC-V port specific,
maybe you need approval from Richard Biener.
On Wed, Aug 26, 2020 at 12:33 AM Maciej W. Rozycki via Gcc-p
77 matches
Mail list logo
