OK.
On Wed, Aug 28, 2019 at 7:56 PM Marek Polacek wrote:
>
> On Wed, Aug 28, 2019 at 04:08:39PM -0400, Jason Merrill wrote:
> > On 8/26/19 1:46 PM, Marek Polacek wrote:
> > > +Wvolatile
> > > +C++ ObjC++ Var(warn_volatile) Warning
> > > +Warn about certain uses of volatile qualifier.
> >
> >
Hi,
This is a rebased patch on trunk for PR78736. The last time, it got
stuck, because of warning issues with libgfortran, for which I filed
PR91593. The patch relegates the warning to Wextra instead, which only
triggers (non-fatal) warnings in libgfortran/io/transfer.c, and
survives
On Wed, Aug 28, 2019 at 04:08:39PM -0400, Jason Merrill wrote:
> On 8/26/19 1:46 PM, Marek Polacek wrote:
> > +Wvolatile
> > +C++ ObjC++ Var(warn_volatile) Warning
> > +Warn about certain uses of volatile qualifier.
>
> Maybe "deprecated uses"?
Ok, changed.
> > --- gcc/cp/expr.c
> > +++
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
Hi!
Thanks for splitting things out, that makes it easier to understand.
On Mon, Aug 26, 2019 at 04:10:22PM -0400, Michael Meissner wrote:
> This code attempts to make this clearer by moving the settings for
> GPRs, FPRs, and traditional Altivec registers to separate functions.
They are called
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
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-*-*
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
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.
*
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:
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
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
* 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
[Differences from V4:
. Use only two register classes: NO_REGS and ALL_REGS.
. Keep same handling of special cases Init="" and Init="-1" in
integer_range_info.
. Skip tests pr70061.c and pr39928-1.c, which are now (correctly)
failing due to the fixed bpf_function_arg_advance.
. Fix constraint
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.
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
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:
On 8/28/19 2:07 PM, Christophe Lyon wrote:
> Hi,
>
> This patch causes an ICE when building libgcc's unwind-arm.o
> when configuring GCC:
> --target arm-none-linux-gnueabihf --with-mode thumb --with-cpu
> cortex-a15 --with-fpu neon-vfpv4:
>
> The build works for the same target, but --with-mode
Note, there is a minor error in this patch. However, since I will need to
create V4 patches shortly, I will fix the bug in those patches.
--
Michael Meissner, IBM
IBM, M/S 2506R, 550 King Street, Littleton, MA 01460-6245, USA
email: meiss...@linux.ibm.com, phone: +1 (978) 899-4797
On Wed, Aug 28, 2019 at 12:14:58PM -0500, Segher Boessenkool wrote:
> Hi Mike,
>
> On Mon, Aug 26, 2019 at 03:54:14PM -0400, Michael Meissner wrote:
> > @@ -1626,8 +1626,8 @@ (define_predicate "small_toc_ref"
> >return GET_CODE (op) == UNSPEC && XINT (op, 1) == UNSPEC_TOCREL;
> > })
> >
>
* config/abi/post/i386-linux-gnu/baseline_symbols.txt: Update.
* config/abi/post/i486-linux-gnu/baseline_symbols.txt: Update.
* config/abi/post/powerpc-linux-gnu/baseline_symbols.txt: Update.
* config/abi/post/powerpc64-linux-gnu/32/baseline_symbols.txt: Update.
On 8/22/19 3:31 PM, Jeff Law wrote:
On 8/20/19 8:10 PM, Martin Sebor wrote:
Jeff,
Please let me know if you agree/disagree and what I need to
do to advance this work:
https://gcc.gnu.org/ml/gcc-patches/2019-08/msg00643.html
For the official record, I agree :-)
Great! :)
Any
On Wed, Aug 28, 2019 at 04:15:54PM -0400, Jason Merrill wrote:
> OK, thanks.
Thanks! I've now updated wwwdocs:
Index: gcc-10/changes.html
===
RCS file: /cvs/gcc/wwwdocs/htdocs/gcc-10/changes.html,v
retrieving revision 1.11
diff -u
This libgo patch moves the osinit code to Go. This is a step toward
updating libgo to 1.13. This adds the 1.13 version of the osinit
function to Go code, and removes the corresponding code from the C
runtime. This should simplify future updates. Some additional 1.13
code was brought in to
On 8/28/19 12:29 PM, Martin Liška wrote:
The patch restores behavior before r265711 where we used
cxx_printable_name for __PRETTY_FUNCTION__.
Patch can bootstrap on x86_64-linux-gnu and survives regression tests.
Ready to be installed?
Thanks,
Martin
gcc/c-family/ChangeLog:
2019-08-27
On 8/27/19 11:24 AM, Marek Polacek wrote:
On Fri, Aug 23, 2019 at 03:10:37PM -0700, Jason Merrill wrote:
+/* True if DECL is declared 'constinit'. */
+#define DECL_DECLARED_CONSTINIT_P(DECL) \
+ DECL_LANG_FLAG_0 (VAR_DECL_CHECK (STRIP_TEMPLATE (DECL)))
Hmm, given that 'constinit' only
On 8/27/19 4:09 AM, Paolo Carlini wrote:
Hi,
by adding a location_t parameter we can improve the locations of the
error messages. At the moment the locations of the first and third
message end up being input_location anyway, but we can imagine improving
those later (this a much more general
On 8/26/19 1:46 PM, Marek Polacek wrote:
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
Hi Bernhard,
On 08/28/19 20:57, Bernhard Reutner-Fischer wrote:
> I see that you copied the unfortunate error-message "commence a loop"
> and i see that i completely forgot to adjust it as per Mike's
> preference in
> https://gcc.gnu.org/ml/fortran/2015-05/msg00166.html
>
> So can you please
Hi.
These 2 files are used for clangd.
I'm going to install the patch.
Martin
ChangeLog:
2019-08-28 Martin Liska
* .gitignore: Add .clangd and compile_commands.json
to .gitignore.
---
.gitignore | 2 ++
1 file changed, 2 insertions(+)
diff --git a/.gitignore
Hi.
The patch restores behavior before r265711 where we used
cxx_printable_name for __PRETTY_FUNCTION__.
Patch can bootstrap on x86_64-linux-gnu and survives regression tests.
Ready to be installed?
Thanks,
Martin
gcc/c-family/ChangeLog:
2019-08-27 Martin Liska
PR c++/91155
Thanks Bernhard.
On Wednesday, August 28, 2019 9:00:36 PM PDT Bernhard Reutner-Fischer wrote:
> On Fri, 23 Aug 2019 17:17:37 -0700
>
> Andrew Benson wrote:
> > This PR is still open - I re-tested the patch on the current trunk. The
> > patch still applies with some line offsets (I've attached
On Fri, 23 Aug 2019 17:17:37 -0700
Andrew Benson wrote:
> This PR is still open - I re-tested the patch on the current trunk. The patch
> still applies with some line offsets (I've attached the updated patch) and
> regtests cleanly. It would be very helpful to me to get this patch committed
>
On Tue, 27 Aug 2019 21:49:38 +0200
Harald Anlauf wrote:
> Committed to trunk as svn revision 274966, after removing some
> accidentally left-over unused variable declarations (copy).
> The actual committed version is attached.
>
> Thanks, Paul, for the quick review!
>
> Unless there are strong
This patch to the Go frontend by Cherry Zhang handles unsafe
conversion expression in escape analysis. Previously escape analysis
never saw these, but now it does for the case of a map assignment.
Bootstrapped and ran Go testsuite on x86_64-pc-linux-gnu. Committed
to mainline.
Ian
Index:
From the modules branch, here are some cleanups inspired by changes
I've made there.
1) directive handling gets a bool arg, not a 0/1 int
2) documented the enumerators of an enum
3) make a bunch of structure flags 1-bit bools.
applying to trunk.
nathan
--
Nathan Sidwell
2019-08-28 Nathan
This patch to the Go frontend and libgo changes the panic message
reported for an out of bounds index or slice operation to include the
invalid values. This makes it easier for the user to see what the
problem is. This implements https://golang.org/cl/161477 in the
gofrontend, for
On Wed, Aug 28, 2019 at 9:35 AM Nathan Sidwell wrote:
>
> My patch reorganizing using decl handling caused a regression in the
> size of debug information. The culprit was that we were passing an
> overload set when previously we'd pass a single decl. And that broke an
> elision test.
>
> Fixed
Hi Mike,
On Mon, Aug 26, 2019 at 03:54:14PM -0400, Michael Meissner wrote:
> @@ -1626,8 +1626,8 @@ (define_predicate "small_toc_ref"
>return GET_CODE (op) == UNSPEC && XINT (op, 1) == UNSPEC_TOCREL;
> })
>
> -;; Return true if the operand is a pc-relative address.
> -(define_predicate
On 8/28/19 9:44 AM, Martin Sebor wrote:
> With the PR 91490 subset committed, attached is what's left
> of the original fix. It seems simple enough that I decided it's
> not worth chopping up any further. The meat of the change is in
> builtins.c. Everything else just adjusts warnings either by
With the PR 91490 subset committed, attached is what's left
of the original fix. It seems simple enough that I decided it's
not worth chopping up any further. The meat of the change is in
builtins.c. Everything else just adjusts warnings either by
making use of it (tree-ssa-strlen.c) or by
The patch for PR 80545 I committed sometime ago in r273771 needs
an additional tweak to be fully effective. Besides a thinko
(using a bitwise OR instead of an AND) it doesn't handle common
options. Attached is this tweak, retested on x86_64-linux.
I will go ahead and commit it shortly.
Martin
Could you, or someone else, commit this for me (as I have no commit access)?
Thanks.
On Mon, Aug 26, 2019, at 11:04 PM, Ian Lance Taylor wrote:
> 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$'
Attached patch improves costing for STV shifts and corrects reject
condition for out of range shift count operands.
2019-08-28 Uroš Bizjak
* config/i386/i386-features.c
(general_scalar_chain::compute_convert_gain):
Correct cost for double-word shifts.
+(define_insn "zero_extendsidi2"
+ [(set (match_operand:DI 0 "register_operand" "=r,r")
+ (zero_extend:DI
+ (match_operand:SI 1 "reg_or_memory_operand" "0,m")))]
+ ""
+ "@
+ mov32\t%0,%1
+ ldxw\t%0,%1"
+ [(set_attr "type" "alu,ldx")])
Auto
> [Differences from V3:
> . Formatting/style fixes:
> + Remove redundant braces.
> + Remove unneeded ATTRIBUTE_UNUSED.
> + Truncate too long lines.
> + Remove an odd line split.
> + Do not break after returns.
> + Use function_arg_info methods instead
On Wed, Aug 28, 2019 at 3:54 PM Richard Biener wrote:
> > >>> 2019-08-23 Richard Biener
> > >>>
> > >>> PR target/91522
> > >>> PR target/91527
> > >>> * config/i386/i386-features.h (general_scalar_chain::defs_map):
> > >>> New member.
> > >>>
On 8/26/19 6:24 AM, Martin Liška wrote:
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
On Wed, 28 Aug 2019, Iain Sandoe wrote:
>
>
>
> > On 26 Aug 2019, at 11:06, Uros Bizjak wrote:
> >
> > 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
Richard Biener writes:
> When making the SLP tree a graph I messed up and in some cases we can
> fail to propagate a higher max_nunits upwards when re-using a subtree.
> For the testcase, but only on the gcc-9-branch, this causes us to
> miss a higher value of 4 completely since it comes from a
>
Hi Christophe,
> After this was committed (r274823), I've noticed 2 regressions on arm*:
> FAIL: gcc.target/arm/pr53447-5.c scan-assembler-times (ldrd|vldr\\.64) 20
> FAIL: gcc.target/arm/pr53447-5.c scan-assembler-times (strd|vstr\\.64) 18
>
> Does this test still pass for you?
You're right,
My patch reorganizing using decl handling caused a regression in the
size of debug information. The culprit was that we were passing an
overload set when previously we'd pass a single decl. And that broke an
elision test.
Fixed by moving that test into the iteration of the overload set.
> On 26 Aug 2019, at 11:06, Uros Bizjak wrote:
>
> 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
On Wed, 28 Aug 2019 at 11:42, Kyrill Tkachov
wrote:
>
>
> On 8/28/19 10:38 AM, Bernd Edlinger wrote:
> > On 8/27/19 11:25 AM, Kyrill Tkachov wrote:
> >> Hi Bernd,
> >>
> >> On 8/15/19 8:47 PM, Bernd Edlinger wrote:
> >>> Hi,
> >>>
> >>> this is the split out part from the "Fix not 8-byte aligned
> jemarch@termi:~/gnu/src/gcc-git/build-bpf/gcc$ PATH=.:$PATH ./xgcc -O2 -c
/home/jemarch/gnu/src/gcc-git/gcc/testsuite/gcc.c-torture/compile/pr39928-2.c
> during RTL pass: ira
>
/home/jemarch/gnu/src/gcc-git/gcc/testsuite/gcc.c-torture/compile/pr39928-2.c:
In function ‘vq_nbest’:
On Tue, Aug 27, 2019 at 3:15 PM Martin Jambor wrote:
>
> Hi,
>
> Feng Xue read through much of ipa-cp.c and ipa-prop.c and reported a few
> redundancies and small errors in PR 91468. The patch below fixes all of
> them, specifically:
>
> 1) A typo in ipcp_modif_dom_walker::before_dom_children
> function integer_range_info(range_option, init, option)
> {
> if (range_option != "") {
> - start = nth_arg(0, range_option);
> - end = nth_arg(1, range_option);
> + init = init + 0;
> + start = nth_arg(0, range_option) + 0;
> +
When making the SLP tree a graph I messed up and in some cases we can
fail to propagate a higher max_nunits upwards when re-using a subtree.
For the testcase, but only on the gcc-9-branch, this causes us to
miss a higher value of 4 completely since it comes from a
single widening stmt which we
On Wed, Aug 28, 2019 at 8:45 AM Jakub Jelinek wrote:
>
> Hi!
>
> The following two testcases FAIL to be vectorized, because SSE2 doesn't have
> many permutation instructions and the one that actually works (whole vector
> shifts) aren't enabled for the V4SFmode.
>
> The following patch fixes it
On 8/28/19 10:38 AM, Bernd Edlinger wrote:
On 8/27/19 11:25 AM, Kyrill Tkachov wrote:
Hi Bernd,
On 8/15/19 8:47 PM, Bernd Edlinger wrote:
Hi,
this is the split out part from the "Fix not 8-byte aligned ldrd/strd on ARMv5 (PR
89544)"
which is sanitizing the middle-end interface to the
On 8/27/19 11:25 AM, Kyrill Tkachov wrote:
> Hi Bernd,
>
> On 8/15/19 8:47 PM, Bernd Edlinger wrote:
>> Hi,
>>
>> this is the split out part from the "Fix not 8-byte aligned ldrd/strd on
>> ARMv5 (PR 89544)"
>> which is sanitizing the middle-end interface to the back-end for strict
>>
On Wed, Aug 28, 2019 at 10:14 AM Richard Biener wrote:
>
>
> STV is interested in DU/UD chains only but for some reason
> (since first patch submission) adds MD. I can't make any sense
> of this and in fact I miss the difference between RD and MD.
> The only other user of MD is fwprop which says
Hi Kyrill,
On 2019/8/28 16:57, Kyrill Tkachov wrote:
> Hi Shaokun,
>
> On 8/28/19 9:47 AM, Shaokun Zhang wrote:
>> Hi Kyrill,
>>
>> On 2019/8/27 18:16, Kyrill Tkachov wrote:
>>> Hi Shaokun,
>>>
>>> On 8/22/19 3:10 PM, Shaokun Zhang wrote:
The DCache clean & ICache invalidation requirements
Prathamesh Kulkarni writes:
> On Tue, 27 Aug 2019 at 21:14, Richard Sandiford
> wrote:
>>
>> Richard should have the final say, but some comments...
>>
>> Prathamesh Kulkarni writes:
>> > diff --git a/gcc/tree-vect-stmts.c b/gcc/tree-vect-stmts.c
>> > index 1e2dfe5d22d..862206b3256 100644
>> >
Hi Shaokun,
On 8/28/19 9:47 AM, Shaokun Zhang wrote:
Hi Kyrill,
On 2019/8/27 18:16, Kyrill Tkachov wrote:
Hi Shaokun,
On 8/22/19 3:10 PM, Shaokun Zhang wrote:
The DCache clean & ICache invalidation requirements for instructions
to be data coherence are discoverable through new fields in
Hi Kyrill,
On 2019/8/27 18:16, Kyrill Tkachov wrote:
> Hi Shaokun,
>
> On 8/22/19 3:10 PM, Shaokun Zhang wrote:
>> The DCache clean & ICache invalidation requirements for instructions
>> to be data coherence are discoverable through new fields in CTR_EL0.
>> Let's support the two bits if they
STV is interested in DU/UD chains only but for some reason
(since first patch submission) adds MD. I can't make any sense
of this and in fact I miss the difference between RD and MD.
The only other user of MD is fwprop which says
/* We use the multiple definitions problem to compute our
"Jose E. Marchesi" writes:
> [Differences from V3:
> . Formatting/style fixes:
> + Remove redundant braces.
> + Remove unneeded ATTRIBUTE_UNUSED.
> + Truncate too long lines.
> + Remove an odd line split.
> + Do not break after returns.
> + Use function_arg_info methods instead of
jose.march...@oracle.com (Jose E. Marchesi) writes:
> > +(define_expand "zero_extendsidi2"
> > + [(set (match_operand:DI 0 "register_operand")
> > + (zero_extend:DI (match_operand:SI 1
> "reg_or_indirect_memory_operand")))]
> > + ""
> > +{
> > +
Hello, gentle maintainer.
This is a message from the Translation Project robot.
A revised PO file for textual domain 'gcc' has been submitted
by the Spanish team of translators. The file is available at:
https://translationproject.org/latest/gcc/es.po
(This file, 'gcc-9.1.0.es.po', has
On Wed, Aug 28, 2019 at 02:05:58AM -0500, Segher Boessenkool wrote:
> On Tue, Aug 27, 2019 at 05:09:52AM -0500, Segher Boessenkool wrote:
> > On Tue, Aug 27, 2019 at 11:12:32AM +0200, Robin Dapp wrote:
> > > as announced in the wrapped-binop gimple patch mail, on s390 we still
> > > emit odd code
On Wed, Aug 28, 2019 at 1:01 AM Steve Kargl
wrote:
>
> The attached ptch implements additional checks on the
> ORDER dummy argument for the RESHAPE intrinsic function.
> Built and regression tested on x86_64-*-freebsd. OK to
> commit?
Ok.
--
Janne Blomqvist
On Tue, Aug 27, 2019 at 05:09:52AM -0500, Segher Boessenkool wrote:
> On Tue, Aug 27, 2019 at 11:12:32AM +0200, Robin Dapp wrote:
> > as announced in the wrapped-binop gimple patch mail, on s390 we still
> > emit odd code in front of loops:
>
> >aghi%r1,-8
> >srlg%r1,%r1,3
> >
On Wed, Aug 28, 2019 at 3:37 AM Steve Kargl
wrote:
>
> The attached patch has been built and tested on x86_64-*-freebsd.
> It adds additional checks for the status dummy argument, and
> therby prevents an ICE. OK to commit?
Ok.
--
Janne Blomqvist
Hi!
The following two testcases FAIL to be vectorized, because SSE2 doesn't have
many permutation instructions and the one that actually works (whole vector
shifts) aren't enabled for the V4SFmode.
The following patch fixes it by enabling those optabs also for V4SFmode (and
V2DFmode). Strictly
75 matches
Mail list logo
