On Thu, Jan 28, 2016 at 03:41:29PM +0100, Jakub Jelinek wrote:
> On Thu, Jan 28, 2016 at 01:40:12PM +0100, Dominik Vogt wrote:
> > -#if defined (__STDC_VERSION__) && __STDC_VERSION__ >= 199901L
> > +#if (defined (__STDC_VERSION__) && __STDC_VERSION__ >= 199901L) \
> > + || (defined (__cplusplus)
On Thu, Jan 28, 2016 at 12:26:38PM -0600, James Norris wrote:
> I think the attached change is what you had in mind with
> regard to doing the check at gimplification time.
Nope, this is still a wrong location for that.
If you look at the next line after the block you've added, you'll see
if (gimp
On Fri, Jan 29, 2016 at 09:27:46AM +0100, Dominik Vogt wrote:
> On Thu, Jan 28, 2016 at 03:41:29PM +0100, Jakub Jelinek wrote:
> > On Thu, Jan 28, 2016 at 01:40:12PM +0100, Dominik Vogt wrote:
> > > -#if defined (__STDC_VERSION__) && __STDC_VERSION__ >= 199901L
> > > +#if (defined (__STDC_VERSION__
I am testing the following patch to fix a regression that we no longer
remove some empty loops.
Bootstrap and regtest running on x86_64-unknown-linux-gnu.
Richard.
2016-01-19 Richard Biener
PR tree-optimization/69547
* tree-ssa-dce.c (mark_aliased_reaching_defs_necessary_1):
On Fri, Jan 29, 2016 at 09:40:48AM +0100, Richard Biener wrote:
> I am testing the following patch to fix a regression that we no longer
> remove some empty loops.
Doesn't this mean that DCE will remove the clobbers as unnecessary, even
when they aren't in empty loops?
Jakub
On Wed, Jan 27, 2016 at 09:22:19AM -0500, David Malcolm wrote:
> On Wed, 2016-01-27 at 12:01 +0100, Dominik Vogt wrote:
> > The attached patch removes a blank line after an error message.
> > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69006
>
> Presumably this was exposed by the stricter testing
The attached patch replaces %qs instead of %s in an error message,
adds %qs to another and fixes indentation in one of the messages.
Compiled and checked that no tests rely on the changed error
messages on a zEC12.
Ciao
Dominik ^_^ ^_^
--
Dominik Vogt
IBM Germany
gcc/ChangeLog
* con
On Fri, 29 Jan 2016, Jakub Jelinek wrote:
> On Fri, Jan 29, 2016 at 09:40:48AM +0100, Richard Biener wrote:
> > I am testing the following patch to fix a regression that we no longer
> > remove some empty loops.
>
> Doesn't this mean that DCE will remove the clobbers as unnecessary, even
> when t
On Mon, Jan 11, 2016 at 03:40:56PM +0100, Dominik Vogt wrote:
> Another patch reducing the accuracy required in the bessel_6 test.
Fixes the test case for S/390. Can this be committed?
> gcc/testsuite/ChangeLog
>
> * gfortran.dg/bessel_6.f90: Reduce accuracy for S/390.
> >From 70a35dd6f6
On Fri, Jan 29, 2016 at 09:27:46AM +0100, Dominik Vogt wrote:
> gcc/ChangeLog
>
> PR c++/69462
> * ginclude/float.h: Also provide FLT_EVAL_METHOD and DECIMAL_DIG for
> C++-11.
Applied. Thanks!
-Andreas-
On Wed, Jan 27, 2016 at 11:04:32AM +0100, Dominik Vogt wrote:
> gcc/testsuite/ChangeLog
>
> * gcc.dg/tree-ssa/ssa-dom-cse-2.c: Require a hardware vector support for
> test to succeed.
Applied. Thanks!
-Andreas-
On Wed, Jan 27, 2016 at 12:01:26PM +0100, Dominik Vogt wrote:
> gcc/ChangeLog
>
> PR other/69006
> * config/s390/s390-c.c (s390_resolve_overloaded_builtin): Remove
> trailing blank line from error message.
Applied. Thanks!
-Andreas-
On Fri, Jan 29, 2016 at 10:06:47AM +0100, Dominik Vogt wrote:
> gcc/ChangeLog
>
> * config/s390/s390-c.c (s390_resolve_overloaded_builtin): Format
> declaration name with %qs and print it in both error messages. Also
> fix indentation.
Applied. Thanks!
-Andreas-
On 01/28/2016 03:15 PM, Jakub Jelinek wrote:
+ if (TREE_CODE (decl) == FUNCTION_DECL
+ && DECL_INITIAL (decl) == 0
+ && DECL_EXTERNAL (decl)
+ && !TREE_PUBLIC (decl)
+ && !DECL_ARTIFICIAL (decl)
+ && !TREE_NO_WARNING (decl))
Do we need to
This patch improves the allocation of registers in the given function. The
allocation
is optimized for the conditional branches. The temporary register used in the
conditional branches to store the comparison results and use of temporary in the
conditional branch is optimized. Such temporary regi
On Thu, Jan 28, 2016 at 09:51:34PM -0500, Jason Merrill wrote:
> On 01/28/2016 03:15 PM, Jakub Jelinek wrote:
> >+if (TREE_CODE (decl) == FUNCTION_DECL
> >+&& DECL_INITIAL (decl) == 0
> >+&& DECL_EXTERNAL (decl)
> >+&& !TREE_PUBLIC (decl)
> >+&& !DECL_ARTIFICIAL
On 01/29/2016 11:35 AM, Jakub Jelinek wrote:
On Thu, Jan 28, 2016 at 09:51:34PM -0500, Jason Merrill wrote:
On 01/28/2016 03:15 PM, Jakub Jelinek wrote:
+ if (TREE_CODE (decl) == FUNCTION_DECL
+ && DECL_INITIAL (decl) == 0
+ && DECL_EXTERNAL (decl)
+ && !TREE
Another target that doesn't have the necessary weak ref support for
the TM-aware exception-handling.
Bootrapped successfully by the reporter, committed to trunk.
commit b7e2e38ab1d938ee19280eba11ed3643a140f86d
Author: Jonathan Wakely
Date: Fri Jan 29 10:38:45 2016 +
Fix Cygwin bootstr
Hi,
The section "12.3.2 Preserving the virtual SSA form" in GCC Internals
is outdated. The two functions it documents push_stmt_changes and
pop_stmt_changes have been removed. The functionality have been
replaced with update_stmt. update_stmt is documented elsewhere in
internals. I therefore propo
Let's say we have
struct a {
int x[1];
int y[1];
} x = { 0, { 0 } };
^
When we reach the marked brace, we call into push_init_level, where we
notice that we have implicit initializers (for x[]) lying around that we
should deal with now that we've seen another open brace. The probl
This patch corrects some tests that can fail with -frename-registers.
The problems typically are of the form "xmm[0-7]+", disallowing
registers 8 and 9, and "xmm[0-9]". disallowing numbers higher than 9.
Most the patch was automatically generated, but there were some other
cases as well.
Enab
Hello!
> * gcc.target/i386/avx512bw-vptestmb-1.c: Correct [xyz]mm register
> number scans.
> * gcc.target/i386/avx512bw-vptestmw-1.c: Likewise.
> * gcc.target/i386/avx512bw-vptestnmb-1.c: Likewise.
> * gcc.target/i386/avx512bw-vptestnmw-1.c: Likewise.
> * gcc.target/i386/avx512cd-vpbroadcastmb2q-1
On 28/01/16 15:42 +0100, Jakub Jelinek wrote:
On Thu, Jan 28, 2016 at 01:32:18PM +, Jonathan Wakely wrote:
On 28/01/16 13:40 +0100, Dominik Vogt wrote:
>The attached patch (written by Jonathan, not me) makes
>FLT_EVAL_METHOD and DECIMAL_DIG available in C++-11 as they should
>be.
>
>https://
On Fri, Jan 29, 2016 at 11:35:07AM +0100, Jakub Jelinek wrote:
> I can try to stick there an assert whether for FUNCTION_DECL
> (DECL_INITIAL (decl) == 0) == DECL_EXTERNAL (decl).
Tried that, but cancelled that quickly, I see lots of cases where
DECL_INITIAL is non-NULL, but DECL_EXTERNAL is set,
Hi,
On Fri, Dec 18, 2015 at 08:41:41AM -0500, David Edelsohn wrote:
> I am pleased to announce that the GCC Steering Committee has
> appointed Martin Jambor as HSA maintainer.
>
> Please join me in congratulating Martin on his new role.
> Martin, please update your listing in the MAIN
Hi Marcin,
sorry for the late feedback.
A few comments regarding the split stack implementation:
The GNU coding style requires to replace every 8 leading blanks on a
line with a tab. There are many lines in your patch violating this.
In case you are an emacs user `whitespace-cleanup' will fix t
> This is OK now.
Committed as SVN 232980.
Regards,
Andrew
Hi!
This PR has been fixed by the PR68701, I've committed
the testcase as obvious to trunk.
2016-01-29 Jakub Jelinek
PR target/66137
* gcc.target/i386/pr66137.c: New test.
--- gcc/testsuite/gcc.target/i386/pr66137.c.jj 2016-01-29 15:05:19.804958974
+0100
+++ gcc/testsuite/g
Uros,
Here is update patch which includes (1) couple changes proposed by
Richard in tree-vect-loop.c and (2) the changes in back-end proposed
by you.
Is it OK for trunk?
Bootstrap and regression testing dis not show any new failures.
ChangeLog:
2016-01-29 Yuri Rumyantsev
PR middle-end/68542
On 01/29/16 02:48, Richard Biener wrote:
I see. Is it possible to simply scrub the whole OACC region in this
case instead?
Do you mean jettison the body of the offloaded fn, or something else? I guess
the former's doable. (Throwing away the fn entirely could result in unresolved
symbol er
Hi!
As the testcase shows, wide_int unsigned division is broken for > 64bit
precision division of unsigned dividend which have 63rd bit set, and all
higher bits cleared (thus is normalized as 2 HWIs, first with MSB set,
the second 0) and divisor of 1, we return just a single HWI, which is
equivale
Hi all,
In this PR we ICE during combine when trying to propagate a comparison into a
vec_duplicate,
that is we end up creating the rtx:
(vec_duplicate:V4SI (eq:CC_NZ (reg:CC_NZ 66 cc)
(const_int 0 [0])))
The documentation for vec_duplicate says:
"The output vector mode must have the sa
Hi all,
Similar to aarch64, the arm port also suffers from PR target/69161 when combine
tries to propagate a CCmode comparison into a vec_duplicate, creating invalid
RTL that ICEs.
Please refer to the PR and the aarch64 fix for more info.
The fix for arm is very similar.
We define a new predicate
Hi!
The following patch fixes a bug in the V4SImode ix86_expand_vector_set
SSE1 handling, before we recurse, we need to copy the original target
to the temporary, otherwise we set just the single element and leave
the rest of the elements uninitialized.
Bootstrapped/regtested on x86_64-linux and
2016-01-28 17:54 GMT-03:00 Joseph Myers :
> Any patch adding a new option needs to add documentation for it to
> invoke.texi (both substantive documentation, and inclusion in the summary
> lists of options).
>
> --
> Joseph S. Myers
> jos...@codesourcery.com
Hi,
Thanks for the feedback, I've just
Hi,
this is a followup to comments by Jakub and Richi on handling of
memory models in HSA atomic operations:
- I have made user-visible diagnostics lower case simple words, rather
than constant identifiers.
- I have added masking by MEMMODEL_BASE_MASK where appropriate.
- I have made sure tha
On Mon, 11 Jan 2016, Alexander Monakov wrote:
> On Mon, 11 Jan 2016, Thomas Schwinge wrote:
> > Alexander, would you please also submit a fix for that for nvptx-tools'
> > nvptx-run.c? (Or want me to do that?)
>
> I can do that, along with another small change I used for -mgomp testing.
I have
On 29.01.2016 02:09, Bernd Schmidt wrote:
> On 01/28/2016 12:36 AM, Eric Botcazou wrote:
>>> [cc-ing Eric as RTL maintainer]
>>
>> Sorry for the delay, the message apparently bounced]
>>
>>> IMO the problem is that rtx_addr_can_trap_p_1 duplicates a large
>>> bit of LRA/reload logic:
>>>
>>> [...]
On Thu, Jan 28, 2016 at 10:38:51AM -0500, Nathan Sidwell wrote:
> This patch adds default compute dimension handling. Users rarely specify
> compute dimensions, expecting the toolchain to DTRT. More savvy users would
> like to specify global defaults. This patch permits both.
Isn't it better to
On Fri, Jan 29, 2016 at 02:09:25AM +0100, Bernd Schmidt wrote:
> I'm on the fence; I do think the original problem is an issue we should fix,
> but I'm also not terribly happy with the implementation we have right now.
The fact that it has been only reported from generated testcases only means
we
On 29/01/16 14:33, Andreas Krebbel wrote:
Hi Marcin,
sorry for the late feedback.
A few comments regarding the split stack implementation:
The GNU coding style requires to replace every 8 leading blanks on a
line with a tab. There are many lines in your patch violating this.
In case you are a
On 01/29/2016 04:41 PM, Jakub Jelinek wrote:
On Fri, Jan 29, 2016 at 02:09:25AM +0100, Bernd Schmidt wrote:
I think a better approach might be to just mark accesses at known locations
in the frame, or arg pushes, as MEM_NOTRAP_P, and consider accesses with
non-constant or calculated offsets as
On Fri, Jan 29, 2016 at 3:13 PM, Yuri Rumyantsev wrote:
> Uros,
>
> Here is update patch which includes (1) couple changes proposed by
> Richard in tree-vect-loop.c and (2) the changes in back-end proposed
> by you.
>
> Is it OK for trunk?
> Bootstrap and regression testing dis not show any new fa
* config/isl.m4: Add comments about isl-0.16.
* configure: Regenerate.
gcc/
* doc/install.texi: Document that isl-0.16 is supported.
---
config/isl.m4| 6 +++---
configure| 12 ++--
gcc/doc/install.texi | 2 +-
3 files changed, 10 insertions(+
On 01/29/2016 04:43 PM, Marcin Kościelnicki wrote:
> The testsuite with -fsplit-stack already hits all of them, and checking
> them manually is rather tricky (I don't know if it could be done in
> target-independent way at all), but I think it'd be reasonable to make
> assembly testcases calling
On Thu, May 28, 2015 at 1:07 PM, Jeff Law wrote:
> On 05/28/2015 06:29 AM, Martin Liška wrote:
>
>>>
>>
>> Hello.
>>
>> Thank you for pointing about missing copyright.
>> Following patch adds that.
>>
>> Ready for trunk?
>
> Yes.
> jeff
>
It looks like this patch was never committed. gcc/mem-sta
Hi,
Function fold_binary_loc calls split_tree to split a tree into constant,
literal and variable parts. Function split_tree deals with minus_expr by
negating different parts into NEXGATE_EXPR. Since tree exprs fed to split_tree
are with NOP conversions stripped, this could result in illegal e
Since 4c4a180d, LTO has turned off flag_pic when linking a fixed
position executable. This results in flag_pic being zero in
rs6000_file_start, and no definition of ".LCTOC1".
However, when we get to actually emitting code, flag_pic may be on
again, and references made to ".LCTOC1". How flag_pic
On 01/29/16 10:18, Jakub Jelinek wrote:
On Thu, Jan 28, 2016 at 10:38:51AM -0500, Nathan Sidwell wrote:
This patch adds default compute dimension handling. Users rarely specify
compute dimensions, expecting the toolchain to DTRT. More savvy users would
like to specify global defaults. This pa
On 29 January 2016 at 05:03, Marek Polacek wrote:
> On Fri, Jan 29, 2016 at 04:46:56AM +0530, Prathamesh Kulkarni wrote:
>> @@ -19016,10 +19017,22 @@ cp_parser_direct_declarator (cp_parser* parser,
>> cp_lexer_consume_token (parser->lexer);
>> /* Peek at the next token. */
>>
On 26/12/15 01:45, Thomas Preud'homme wrote:
[Sending on behalf of Andre Vieira]
Hello,
This patch adds RTL patterns for the push and pop instructions for thumb1.
These are needed by subsequent patches in the series.
*** gcc/ChangeLog ***
2015-10-27 Andre Vieira
Thomas P
On 26/12/15 01:47, Thomas Preud'homme wrote:
[Sending on behalf of Andre Vieira]
Hello,
This patch adds support for the ARMv8-M Security Extensions
'cmse_nonsecure_entry' attribute. In this patch we implement the attribute
handling and diagnosis around the attribute. See Section 5.4 of ARM®v8
On 05/01/16 14:38, Andre Vieira wrote:
On 31/12/15 20:54, Joseph Myers wrote:
On Sat, 26 Dec 2015, Thomas Preud'homme wrote:
+#define CMSE_TT_ASM(flags) \
+{ \
+ cmse_address_info_t result; \
+ __asm__ ("tt" # flags " %0,%1" \
+ : "=r"(result) \
+ : "r"(p) \
+ : "memory");
On 26/12/15 01:52, Thomas Preud'homme wrote:
[Sending on behalf of Andre Vieira]
Hello,
This patch extends support for the ARMv8-M Security Extensions
'cmse_nonsecure_entry' attribute in two ways:
1) Generate two labels for the function, the regular function name and one with
the function's
On 26/12/15 01:54, Thomas Preud'homme wrote:
[Sending on behalf of Andre Vieira]
Hello,
This patch extends support for the ARMv8-M Security Extensions
'cmse_nonsecure_entry' attribute to safeguard against leak of information
through unbanked registers.
When returning from a nonsecure entry f
On 26/12/15 01:55, Thomas Preud'homme wrote:
[Sending on behalf of Andre Vieira]
Hello,
This patch adds support for the ARMv8-M Security Extensions
'cmse_nonsecure_call' attribute. This attribute may only be used for function
types and when used in combination with the '-mcmse' compilation fl
On 26/12/15 01:59, Thomas Preud'homme wrote:
[Sending on behalf of Andre Vieira]
Hello,
This patch adds support ARMv8-M's Security Extension's cmse_nonsecure_caller
intrinsic. This intrinsic is used to check whether an entry function was called
from a non-secure state.
See Section 5.4.3 of AR
On 19/01/16 15:28, Andre Vieira (lists) wrote:
On 16/01/16 14:49, Senthil Kumar Selvaraj wrote:
User-agent: mu4e 0.9.13; emacs 24.5.1
Hi,
Apologies for the bad posting style (I don't have the
original email handy), but shouldn't _gnu_cmse_nonsecure_call be defined
with the .global directive in
So PR57193 has an example of sub-optimal code generation, with some
unnecessary register moves left after LRA. These seem to be difficult to
prevent, but last year Robert Suchanek made some modifications to
regrename that allow it to clean up such cases. Enabling
-frename-registers removes one
On 28.01.2016 23:17, Richard Sandiford wrote:
> Bernd Edlinger writes:
>> On 26.01.2016 22:18, Richard Sandiford wrote:
>>> [cc-ing Eric as RTL maintainer]
>>>
>>> Matthew Fortune writes:
Bernd Edlinger writes:
> Matthew Fortune writes:
>> Has the patch been tested beyond just buil
On 01/29/2016 02:31 AM, Ajit Kumar Agarwal wrote:
This patch improves the allocation of registers in the given function. The
allocation
is optimized for the conditional branches. The temporary register used in the
conditional branches to store the comparison results and use of temporary in the
in ix86_split_long_move (i386.c:24353) with -fno-split-wide-types -mavx
Reply-To: "H.J. Lu"
r229087, which caused PR 69530, was supposed to fix PR 67609. r229458
has made r229087 unnecessary.
Approved by Vladimir in PR 69530. Checked into trunk.
H.J.
---
gcc/
PR target/69530
On Thu, Jan 28, 2016 at 5:41 PM, Bill Schmidt
wrote:
> Hi,
>
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65546 identifies a failure
> in gcc.dg/vect/costmodel/ppc/costmodel-vect-31a.c. The test case hasn't
> kept up with changes in the vectorizer, so it's looking for the wrong
> error message.
Hi all,
attached is a patch to fix a regression in current gfortran when a
coarray is used in the source=-expression of an allocate(). The ICE was
caused by the class information, i.e., _vptr and so on, not at the
expected place. The patch fixes this.
The patch also fixes pr69418, which I will fl
On Fri, Jan 29, 2016 at 11:38 AM, Alan Modra wrote:
> Since 4c4a180d, LTO has turned off flag_pic when linking a fixed
> position executable. This results in flag_pic being zero in
> rs6000_file_start, and no definition of ".LCTOC1".
>
> However, when we get to actually emitting code, flag_pic ma
On 01/28/2016 09:07 AM, Vladimir Makarov wrote:
On 01/28/2016 08:05 AM, Jakub Jelinek wrote:
On Wed, Jan 27, 2016 at 04:01:23PM -0500, Vladimir Makarov wrote:
The following patch fixes PR69299.
The details of the problem is described on
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69299
On January 29, 2016 6:34:50 PM GMT+01:00, Bernd Schmidt
wrote:
>So PR57193 has an example of sub-optimal code generation, with some
>unnecessary register moves left after LRA. These seem to be difficult
>to
>prevent, but last year Robert Suchanek made some modifications to
>regrename that allo
The following patch is the final version of the patch for
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69299
The patch was approved by Richard Henderson and Jakub.
Committed as rev. 232993.
Index: ChangeLog
===
--- ChangeLog
Hi!
We ICE on the following testcase, because the C FE abuses TYPE_VFIELD
for its FE stuff, but may leak it to the middle-end.
We clear it for TYPE_MAIN_VARIANT (and only use it for that), but
for the other variants it could be non-NULL, because build_variant_type*
would just copy that field over.
On 29.01.2016 16:47 Bernd Schmidt wrote:
> On 01/29/2016 04:41 PM, Jakub Jelinek wrote:
>> On Fri, Jan 29, 2016 at 02:09:25AM +0100, Bernd Schmidt wrote:
>
>>> I think a better approach might be to just mark accesses at known
>>> locations
>>> in the frame, or arg pushes, as MEM_NOTRAP_P, and consi
Hi!
This patch reverts one tiny change from r228049 changes (which hasn't been
mentioned in the ChangeLog or patch description). We definitely need to
revisit this for GCC 7, but stage4 is probably not the right time for that,
and the patch fixes e.g. tons of warnings (or with -Werror errors on
i
On 29/01/16 17:01, Prathamesh Kulkarni wrote:
Thanks for the review. AFAIK the type-qualifiers would be const,
restrict, volatile and _Atomic (n1570 p 6.7.3) ?
I added a check for those and for variable length array.
I am having issues with writing the test-case,
some cases pass with -std=c++11 b
On Fri, Jan 29, 2016 at 08:41:18PM +0100, Jakub Jelinek wrote:
> Hi!
>
> We ICE on the following testcase, because the C FE abuses TYPE_VFIELD
> for its FE stuff, but may leak it to the middle-end.
> We clear it for TYPE_MAIN_VARIANT (and only use it for that), but
> for the other variants it coul
This is a patch for PR 68273, where MIPS is passing arguments in the wrong
registers. The problem is that when passing an argument by value,
mips_function_arg_boundary was looking at the type of the argument (and
not just the mode), and if that argument was a variable with extra alignment
info (s
These local styles feel a bit odd to begin with, and if we skip
the ... within ..., the originally perceived/
addresses issue should go away.
Unless there are objections from the Fortran side, I plan on
committing this in a couple of days.
Gerald
Index: fortran/index.html
===
Our standard footer also got hit by the (needlessly for for us)
stricter server settings.
This again gets rid of extra vertical space in that box.
Installed, and afterwards I rebuilt our website using the
/www/gcc/bin/preprocess script on gcc.gnu.org.
Gerald
Index: gcc.css
=
On Fri, 2016-01-29 at 20:50 +0100, Jakub Jelinek wrote:
> Hi!
>
> This patch reverts one tiny change from r228049 changes (which hasn't
> been
> mentioned in the ChangeLog or patch description). We definitely need
> to
> revisit this for GCC 7, but stage4 is probably not the right time for
> that
This fixes the worst of what the new server settings broke; our
main page should look quite more reasonable with this. And it
simplifies things a little.
Applied.
Index: index.html
===
RCS file: /cvs/gcc/wwwdocs/htdocs/index.html,v
78 matches
Mail list logo
