> Let me know if I've forgotten anything we should document.
Not your fault, but -Wclass-memaccess comes rather often and is not in the
changes.
Bernd.
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 French team of translators. The file is available at:
http://translationproject.org/latest/gcc/fr.po
(This file, 'gcc-8.1-b20180401.fr.po', h
Committed to CVS (along with a tiny fix for an HTML validation error
in this patch).
Let me know if I've forgotten anything we should document.
? htdocs/gcc-8/.changes.html.swp
Index: htdocs/gcc-8/changes.html
===
RCS file: /cvs/gcc/w
Ok, thanks.
On Apr 10, 2018 4:37 PM, "Marek Polacek" wrote:
On Mon, Apr 09, 2018 at 02:18:16PM -0400, Jason Merrill wrote:
> On Fri, Apr 6, 2018 at 2:17 PM, Marek Polacek wrote:
> > On Mon, Mar 26, 2018 at 01:17:22PM -0400, Jason Merrill wrote:
> >> On Sat, Mar 24, 2018 at 6:59 AM, Marek Polace
Another update to document -mcall- and -mtraceback= options. Cleanup to
remove -mabi={no-,}spe from the RS/6000 and PowerPC section. And a trim
to the help text for -mblock-compare-* and -mstring-compare-inline-
limit so they are not excessively long. The complete description for
those is now in in
On Tue, Apr 10, 2018 at 04:49:44PM -0500, Aaron Sawdey wrote:
> This updates invoke.texi to document -mblock-compare-inline-limit,
> -mblock-compare-inline-loop-limit, and -mstring-compare-inline-limit.
>
> Tested with "make pdf", ok for trunk?
Looks fine, thanks!
Segher
> 2018-04-10 Aaron S
Update to my new email address. Committed as 259301.
2018-04-10 Aaron Sawdey
* MAINTAINERS: Update my email address.
--
Aaron Sawdey, Ph.D. acsaw...@linux.vnet.ibm.com
050-2/C113 (507) 253-7520 home: 507/263-0782
IBM Linux Technology Center - PPC ToolchainIndex: MAINTAINERS
===
Hi Jakub,
The new test FAILs everywhere, gfortran.dg doesn't have infrastructure to
run -fopenmp, -fopenacc nor -ftree-parallelize-loops= tests.
You need to put such tests into libgomp/testsuite/libgomp.fortran/
I put the test case in the attached form into the libgomp.fortran
directory, but
This updates invoke.texi to document -mblock-compare-inline-limit,
-mblock-compare-inline-loop-limit, and -mstring-compare-inline-limit.
Tested with "make pdf", ok for trunk?
2018-04-10 Aaron Sawdey
PR target/85321
* doc/invoke.texi (RS/6000 and PowerPC Options): Document opti
The stack clash protection code had a logic error in how it decided
whether to put the final update size in a register, or to emit it
directly in an insn. This fixes it. It also tidies some surrounding
code.
Segher
2018-04-10 Segher Boessenkool
* gcc/config/rs6000/rs6000.md (alloc
Hi!
On Thu, Apr 05, 2018 at 01:07:21PM -0400, David Edelsohn wrote:
> I don't have a fundamental objection. AIX does use DWARF EH. I'm not
> worried about the EH processing itself, but this may trigger paths in
> dwarf2out, etc. that aren't prepared for AIX XCOFF. I'm concerned that
> it may assu
On Mon, Apr 09, 2018 at 02:18:16PM -0400, Jason Merrill wrote:
> On Fri, Apr 6, 2018 at 2:17 PM, Marek Polacek wrote:
> > On Mon, Mar 26, 2018 at 01:17:22PM -0400, Jason Merrill wrote:
> >> On Sat, Mar 24, 2018 at 6:59 AM, Marek Polacek wrote:
> >> > Recently the code in finish_static_assert was
On 10/04/18 13:12 -0400, Jason Merrill wrote:
In Joseph's patch for bug 52023, making _Alignof(double) 4 rather than
8 on x86, he deliberately didn't change the C++ behavior, based on
this wording in the C++ standard:
--
The alignment required for a type might be different when it is used
as the
OK.
On Tue, Apr 10, 2018 at 2:57 PM, Paolo Carlini wrote:
> Hi,
>
> this isn't a regression, but deciding what we want to do should be easy and
> quick enough. The issue is that "mysteriously" we warn
> -Wzero-as-null-pointer-constant for:
>
> decltype( nullptr ) warn = {};
>
> and we don't for:
Hi,
this isn't a regression, but deciding what we want to do should be easy
and quick enough. The issue is that "mysteriously" we warn
-Wzero-as-null-pointer-constant for:
decltype( nullptr ) warn = {};
and we don't for:
int* no_warn = {};
That's easily explained given the code we have in
On Tue, 2018-04-10 at 13:47 -0400, Nathan Sidwell wrote:
> On 04/10/2018 12:43 PM, Jason Merrill wrote:
> > On Tue, Apr 10, 2018 at 12:32 PM, Nathan Sidwell
> > wrote:
> > > On 04/10/2018 12:00 PM, Jason Merrill wrote:
> > > I don't see why we should warn at all.
> >
> > It's not on by default, b
This updates the help text for some options to mention the allowed
values for -mXX=XX.
Tested on powerpc64-linux {-m32,-m64}; committing.
Segher
2018-04-10 Segher Boessenkool
PR target/85321
* config/rs6000/rs6000.opt (mtraceback=): Show the allowed values in
the he
On 04/10/2018 12:43 PM, Jason Merrill wrote:
On Tue, Apr 10, 2018 at 12:32 PM, Nathan Sidwell wrote:
On 04/10/2018 12:00 PM, Jason Merrill wrote:
I don't see why we should warn at all.
It's not on by default, but some people want to get a warning about
redundant semicolons. Clang also has
On Tue, Apr 10, 2018 at 5:28 PM, Bin.Cheng wrote:
> On Tue, Apr 10, 2018 at 3:58 PM, Bin.Cheng wrote:
>> On Tue, Apr 10, 2018 at 2:26 PM, Jakub Jelinek wrote:
>>> On Tue, Apr 10, 2018 at 09:55:35AM +, Bin Cheng wrote:
Hi Rainer, could you please help me double check that this solves the
On Tue, Apr 10, 2018 at 10:21 AM, Jason Merrill wrote:
> 65821 complains that in this testcase, setting a breakpoint on main()
> ends up stopping at the line with the default argument of foo(). I
> think I agree that the confusion from this debugging experience
> outweighs the usefulness of being
In Joseph's patch for bug 52023, making _Alignof(double) 4 rather than
8 on x86, he deliberately didn't change the C++ behavior, based on
this wording in the C++ standard:
--
The alignment required for a type might be different when it is used
as the type of a complete object and when it is used a
Hi!
On Mon, 26 Mar 2018 14:57:12 -0700, Cesar Philippidis
wrote:
> diff --git a/gcc/testsuite/gcc.target/nvptx/pr85056.c
> b/gcc/testsuite/gcc.target/nvptx/pr85056.c
> new file mode 100644
> index 000..fe7f8af856e
> --- /dev/null
> +++ b/gcc/testsuite/gcc.target/nvptx/pr85056.c
> @@ -0,
On Tue, Apr 10, 2018 at 12:32 PM, Nathan Sidwell wrote:
> On 04/10/2018 12:00 PM, Jason Merrill wrote:
>>
>> On Tue, Apr 10, 2018 at 11:06 AM, Nathan Sidwell wrote:
>
>
>> This is the -Wextra-semi warning that Volker added recently, and your
>> patch would break.
>>
>> Do we want -Wextra-semi to
On 04/10/2018 12:00 PM, Jason Merrill wrote:
On Tue, Apr 10, 2018 at 11:06 AM, Nathan Sidwell wrote:
This is the -Wextra-semi warning that Volker added recently, and your
patch would break.
Do we want -Wextra-semi to now warn about all empty declarations at
class/namespace scope, not just af
On Tue, Apr 10, 2018 at 3:58 PM, Bin.Cheng wrote:
> On Tue, Apr 10, 2018 at 2:26 PM, Jakub Jelinek wrote:
>> On Tue, Apr 10, 2018 at 09:55:35AM +, Bin Cheng wrote:
>>> Hi Rainer, could you please help me double check that this solves the issue?
>>>
>>> Thanks,
>>> bin
>>>
>>> gcc/testsuite
>>
On Tue, Apr 10, 2018 at 11:06 AM, Nathan Sidwell wrote:
> Jason,
> thanks for looking up about empty-decls. This patch implements the C++11
> change.
>
> At namespace-scope & class-scope we're now silent about empty declarations,
> when not in C++-98 mode.
>
> The class-scope change was a little
At present, due bugs in the nvptx state propagation code, worker
partitioning must be deactivated when the user specifies a large
vector_length. However, the code that is responsible for deactivating
worker partitioning was not considering the case where the vector_length
is the size of a warp. Con
On 04/09/2018 06:37 PM, Sandra Loosemore wrote:
On 04/09/2018 05:58 PM, Martin Sebor wrote:
Ping: I will go ahead and commit this patch sometime this
week unless I hear objections:
https://gcc.gnu.org/ml/gcc-patches/2018-04/msg00036.html
This patch is mostly OK, except for these hunks:
Hello,
On 10.04.2018 17:40, Alexander Monakov wrote:
> Hi,
>
> We have this code in sel-sched.c sel_region_init():
>
> 6918 /* Init correct liveness sets on each instruction of a single-block
> loop.
> 6919 This is the only situation when we can't update liveness when
> calling
> 6920
CANNABINOID THERAPEUTICS SYMPOSIUM
June 6 - 7, 2018 | Crowne Plaza Redondo Beach & Marina Hotel | Redondo Beach, CA
---
SIGN UP TODAY:
http://links.infocastevents.mkt8115.com/ctt?kn=5&ms=MzM4MjE3NzgS1&r=NjkyMTk1NzM3MTk0S0&b=2&j=MTI2MTE3NzkyMQS2&mt=1&rt=0
---
Hear from world class scientists an
Hi Jakub,
On Tue, Apr 10, 2018 at 03:50:33PM +0200, Jakub Jelinek wrote:
> The following testcase ICEs, because subst first creates invalid RTL
> (in this case (float:SF (const_int 256))) and only later on simplifies it
> using on the-side op0_mode. In the end try_combine succeeds, so we don't
>
On 04/10/2018 05:06 PM, Segher Boessenkool wrote:
> Hi!
>
> On Tue, Apr 10, 2018 at 02:26:32PM +0200, Martin Liška wrote:
>> It's quite obvious documentation patch does:
>> ./xgcc -B. --help=target 2>&1 | grep mpri
>> -mprioritize-restricted-insns=<0,2> Specify scheduling priority for
>> dispa
Hi!
On Tue, Apr 10, 2018 at 02:26:32PM +0200, Martin Liška wrote:
> It's quite obvious documentation patch does:
> ./xgcc -B. --help=target 2>&1 | grep mpri
> -mprioritize-restricted-insns=<0,2> Specify scheduling priority for
> dispatch slot restricted insns.
Showing this as a range is misle
Jason,
thanks for looking up about empty-decls. This patch implements the
C++11 change.
At namespace-scope & class-scope we're now silent about empty
declarations, when not in C++-98 mode.
The class-scope change was a little more invasive, because we silently
accepted a semicolon after an
On Tue, Apr 10, 2018 at 2:26 PM, Jakub Jelinek wrote:
> On Tue, Apr 10, 2018 at 09:55:35AM +, Bin Cheng wrote:
>> Hi Rainer, could you please help me double check that this solves the issue?
>>
>> Thanks,
>> bin
>>
>> gcc/testsuite
>> 2018-04-10 Bin Cheng
>>
>> PR testsuite/85190
>>
On 04/10/2018 04:10 PM, David Malcolm wrote:
> On Tue, 2018-04-10 at 14:45 +0200, Martin Liška wrote:
>> Hi.
>>
>> I'm bit ashamed that I tasted our gdb pretty-printers today for the
>> first time.
>> It's working nice and I would like to extend it a bit for classes
>> that I print/debug often.
>
Hi,
We have this code in sel-sched.c sel_region_init():
6918 /* Init correct liveness sets on each instruction of a single-block loop.
6919 This is the only situation when we can't update liveness when calling
6920 compute_live for the first insn of the loop. */
6921 if (current_lo
Hi Sameera
On 10/04/18 11:20, Sameera Deshpande wrote:
On 7 April 2018 at 01:25, Christophe Lyon wrote:
Hi,
2018-04-06 12:15 GMT+02:00 Sameera Deshpande :
Hi Christophe,
Please find attached the updated patch with testcases.
Ok for trunk?
Thanks for the update.
Since the new intrinsics
Hi!
The r257510 change broke -gsplit-dwarf support by introducing a circular
dependency. Before that revision index_location_lists used to do:
/* Don't index an entry that has already been indexed
or won't be output. */
if (curr->begin_entry != NULL
On Tue, Apr 10, 2018 at 09:55:35AM +, Bin Cheng wrote:
> Hi Rainer, could you please help me double check that this solves the issue?
>
> Thanks,
> bin
>
> gcc/testsuite
> 2018-04-10 Bin Cheng
>
> PR testsuite/85190
> * gcc.dg/vect/pr81196.c: Adjust pointer for aligned access.
Hi!
Dunno what I was thinking when adding this if (j < i) break;, with it we
never verify whether second and following loop iterators aren't used in
third and following loops in collapse(3) and above loops.
Fixed thusly, bootstrapped/regtested on x86_64-linux and i686-linux,
committed to trunk.
OK.
On Tue, Apr 10, 2018 at 10:10 AM, Jakub Jelinek wrote:
> Hi!
>
> The "Implement P0962" change changed the
> if (member_begin != NULL_TREE || member_end != NULL_TREE)
> condition to
> if (member_begin != NULL_TREE && member_end != NULL_TREE)
> but that created a lot of dead-code, because now t
65821 complains that in this testcase, setting a breakpoint on main()
ends up stopping at the line with the default argument of foo(). I
think I agree that the confusion from this debugging experience
outweighs the usefulness of being able to step through evaluation of a
default argument, so this
On 10 April 2018 at 17:10, Jakub Jelinek wrote:
> Hi!
>
> The "Implement P0962" change changed the
> if (member_begin != NULL_TREE || member_end != NULL_TREE)
> condition to
> if (member_begin != NULL_TREE && member_end != NULL_TREE)
> but that created a lot of dead-code, because now the diagnosti
On Tue, 2018-04-10 at 14:45 +0200, Martin Liška wrote:
> Hi.
>
> I'm bit ashamed that I tasted our gdb pretty-printers today for the
> first time.
> It's working nice and I would like to extend it a bit for classes
> that I print/debug often.
This looks good from the gdbhooks.py side; I'll assume
Hi!
The "Implement P0962" change changed the
if (member_begin != NULL_TREE || member_end != NULL_TREE)
condition to
if (member_begin != NULL_TREE && member_end != NULL_TREE)
but that created a lot of dead-code, because now the diagnostics in that
if is unreachable, we are always guaranteed both me
Checking for a flexible array in a union is currently done by
grokdeclarator, so it wasn't being caught after substitution. I
didn't see a good place to handle it for both cases, and it's small
enough, so I just copied it over.
Tested x86_64-pc-linux-gnu, applying to trunk.
commit e63bd3e7471152b
On Tue, Apr 10, 2018 at 9:50 AM, Jason Merrill wrote:
> On Mon, Apr 9, 2018 at 6:55 PM, Paolo Carlini
> wrote:
>> On 09/04/2018 21:39, Jason Merrill wrote:
>>>
>>> cp_parser_check_template_parameters is supposed to catch when we have
>>> the wrong number of template parameter lists, but it wasn'
On Mon, Apr 9, 2018 at 6:55 PM, Paolo Carlini wrote:
> On 09/04/2018 21:39, Jason Merrill wrote:
>>
>> cp_parser_check_template_parameters is supposed to catch when we have
>> the wrong number of template parameter lists, but it wasn't diagnosing
>> this case. Fixed by checking whether the thing
Hi!
The following testcase ICEs, because subst first creates invalid RTL
(in this case (float:SF (const_int 256))) and only later on simplifies it
using on the-side op0_mode. In the end try_combine succeeds, so we don't
undo anything from the undo buffer, but call propagate_for_debug with the
pat
Hi.
I'm sending obvious follow-up patch that I've just tested on x86_64-linux-gnu.
Martin
>From 5ceff747f5a55fb28ae1e4ef87fc7e39344ae11f Mon Sep 17 00:00:00 2001
From: marxin
Date: Tue, 10 Apr 2018 14:36:40 +0200
Subject: [PATCH] Fix obvious error in handling of error attribute (PR
lto/85248).
On Mon, Apr 09, 2018 at 10:58:13PM +0200, Thomas Koenig wrote:
> 2018-04-09 Thomas Koenig
>
> PR fortran/83064
> * trans-stmt.c (gfc_trans_forall_loop): Remove annotation for
> parallell processing of DO CONCURRENT -ftree-parallelize-loops
> is set.
>
> 2018-04-
Hi!
I'd like to ping the
http://gcc.gnu.org/ml/gcc-patches/2018-04/msg00123.html
P1 PR85177 vinsert[if]{32x4,64x2} pattern fix
patch.
Thanks
Jakub
On 08/03/18 13:32, James Greenhalgh wrote:
On Wed, Mar 07, 2018 at 05:39:41PM +, Kyrill Tkachov wrote:
Hi all,
In this wrong-code PR the combine pass ends up moving a CC-using instruction past a
*compare_cstore_insn
insn_and_split. After reload the *compare_cstore_insn splitter ends up
g
On Tue, Apr 10, 2018 at 12:40 PM, Richard Sandiford
wrote:
> Jakub Jelinek writes:
>> On Mon, Apr 09, 2018 at 06:47:45PM +0100, Richard Sandiford wrote:
>>> In this PR we used WIDEN_SUM_EXPR to vectorise:
>>>
>>> short i, y;
>>> int sum;
>>> [...]
>>> for (i = x; i > 0; i--)
>>> sum +
On Tue, Apr 10, 2018 at 11:55 AM, Bin Cheng wrote:
> Hi,
> Pointer q in gcc.dg/vect/pr81196.c is not aligned after vectorization,
> resulting test failure for some targets.
> This simple patch adjust it so that it's aligned.
>
> Is it OK?
Yes, looks quite obvious.
Richard.
> Hi Rainer, could y
Hi.
I'm bit ashamed that I tasted our gdb pretty-printers today for the first time.
It's working nice and I would like to extend it a bit for classes that I
print/debug often.
gcc/ChangeLog:
2018-04-10 Martin Liska
* gdbhooks.py: Add pretty-printers for varpool_node, symtab_node,
Hello Jakub,
Sorry for missing that.
Your patch is OK.
—
Thanks, K
> On 10 Apr 2018, at 13:59, Jakub Jelinek wrote:
>
> Hi!
>
> I'd like to ping the
> http://gcc.gnu.org/ml/gcc-patches/2018-04/msg00123.html
> P1 PR85177 vinsert[if]{32x4,64x2} pattern fix
> patch.
>
> Thanks
>
> Jaku
On 04/10/2018 11:19 AM, Jakub Jelinek wrote:
> On Mon, Apr 09, 2018 at 02:31:04PM +0200, Martin Liška wrote:
>> gcc/testsuite/ChangeLog:
>>
>> 2018-03-28 Martin Liska
>>
>> * gcc.dg/string-opt-1.c:
>
> I guess you really didn't mean to keep the above entry around, just the one
> below, rig
Hi.
It's quite obvious documentation patch does:
./xgcc -B. --help=target 2>&1 | grep mpri
-mprioritize-restricted-insns=<0,2> Specify scheduling priority for dispatch
slot restricted insns.
gcc/ChangeLog:
2018-04-10 Martin Liska
* config/powerpcspe/powerpcspe.opt: Add IntegerRan
Hi,
The add_branch_dependencies function is fairly unusual in that it creates
dependence edges "out of thin air" for all sorts of instructions preceding
BB end. I think that is really unfortunate (explicit barriers in RTL would
be more natural), but I've already complained about that in the PR.
T
Jakub Jelinek writes:
> On Mon, Apr 09, 2018 at 06:47:45PM +0100, Richard Sandiford wrote:
>> In this PR we used WIDEN_SUM_EXPR to vectorise:
>>
>> short i, y;
>> int sum;
>> [...]
>> for (i = x; i > 0; i--)
>> sum += y;
>>
>> with 4 ints and 8 shorts per vector. The problem was tha
Hi,
this fixes a simple "regression" under the qsort_chk umbrella: sched-deps
analysis has deps->readonly flag, but macro-fusion code does not respect it
and mutates instructions. This breaks an assumption in sel_rank_for_schedule
and manifests as qsort checking error.
Since sched_macro_fuse_insn
On Mon, Apr 09, 2018 at 02:31:04PM +0200, Martin Liška wrote:
> gcc/testsuite/ChangeLog:
>
> 2018-03-28 Martin Liska
>
> * gcc.dg/string-opt-1.c:
I guess you really didn't mean to keep the above entry around, just the one
below, right?
> gcc/testsuite/ChangeLog:
>
> 2018-03-14 Martin
On 7 April 2018 at 01:25, Christophe Lyon wrote:
> Hi,
>
> 2018-04-06 12:15 GMT+02:00 Sameera Deshpande :
>> Hi Christophe,
>>
>> Please find attached the updated patch with testcases.
>>
>> Ok for trunk?
>
> Thanks for the update.
>
> Since the new intrinsics are only available on aarch64, you wa
Hi,
Pointer q in gcc.dg/vect/pr81196.c is not aligned after vectorization,
resulting test failure for some targets.
This simple patch adjust it so that it's aligned.
Is it OK?
Hi Rainer, could you please help me double check that this solves the issue?
Thanks,
bin
gcc/testsuite
2018-04-10 Bin
On Mon, Apr 09, 2018 at 11:50:14PM -0600, Jan Beulich wrote:
> >> As ICC generates the same assembly on the instructions:
> >> mov eax, DWORD PTR k1[rip]
> >> ...
> >> mov eax, DWORD PTR xmm0[rip]
> >> I think either the intel syntax spec is faulty, or gas is buggy and shoul
On Tue, Apr 10, 2018 at 10:45 AM, Richard Earnshaw (lists)
wrote:
>>> Alpha should be fixed -- the docs clearly state that the operand is "the
>>> memory reference in the stack that needs to be probed". Just passing in
>>> the offset seems wrong.
>>
>> This pattern has to be renamed to not clash
On 10/04/18 08:37, Uros Bizjak wrote:
> On Tue, Apr 10, 2018 at 12:26 AM, Jeff Law wrote:
>> On 04/05/2018 08:20 AM, Kyrill Tkachov wrote:
>>> Hi all,
>>>
>>> In this PR the expansion code emits an invalid memory address for the
>>> stack probe, which the backend fails to recognise.
>>> The addres
>>> On 10.04.18 at 08:42, wrote:
> On Mon, Apr 09, 2018 at 11:50:14PM -0600, Jan Beulich wrote:
>> >> As ICC generates the same assembly on the instructions:
>> >> mov eax, DWORD PTR k1[rip]
>> >> ...
>> >> mov eax, DWORD PTR xmm0[rip]
>> >> I think either the intel syntax
On Tue, 10 Apr 2018, Jonathan Wakely wrote:
> Define a new exception type derived from std::ios::failure[abi:cxx11]
> which also aggregates an object of the gcc4-compatible ios::failure
> type. Make __throw_ios_failure throw this new type for iostream errors
> that raise exceptions. Provide custom
On Tue, Apr 10, 2018 at 12:26 AM, Jeff Law wrote:
> On 04/05/2018 08:20 AM, Kyrill Tkachov wrote:
>> Hi all,
>>
>> In this PR the expansion code emits an invalid memory address for the
>> stack probe, which the backend fails to recognise.
>> The address is created explicitly in
>> anti_adjust_stac
72 matches
Mail list logo
