Hi Jim:
Theodore Teah sent an mail say "Your assignment/disclaimer process
with the FSF is currently complete.".
Could you help us to commit that?
Thanks :)
On Fri, Feb 23, 2018 at 2:33 AM, Jim Wilson wrote:
> On Wed, Feb 21, 2018 at 10:34 PM, Kito Cheng wrote:
>> I don't family with copyrigh
On Thu, Apr 05, 2018 at 01:29:06PM +0100, Tamar Christina wrote:
> diff --git a/gcc/expr.c b/gcc/expr.c
> index
> 00660293f72e5441a6421a280b04c57fca2922b8..7daeb8c91d758edf0b3dc37f6927380b6f3df877
> 100644
> --- a/gcc/expr.c
> +++ b/gcc/expr.c
> @@ -2749,7 +2749,7 @@ copy_blkmode_to_reg (machine_
On Thu, 2018-03-29 at 15:25 -0400, Jason Merrill wrote:
> On Thu, Mar 22, 2018 at 7:44 PM, David Malcolm
> wrote:
> > We provide fix-it hints for the most common "std" names when an
> > explicit
> > "std::" prefix is present, however we don't yet provide fix-it
> > hints for
> > this implicit case
Attached is the final version of the patch to adjust the lists
of options (C++ Language Options and -Wall) to include missing
C++ options, reference the forms of options that aren't
the default, and use TexInfo tables for the lists of options
in -Wall and -Wextra to address Nathan's comment. The
OK.
On Thu, Apr 5, 2018 at 5:09 PM, Jakub Jelinek wrote:
> Hi!
>
> For cp_finish_decomp we require that the id decl for the structured binding
> are chained together, because we pass just the artificial underlying decl
> and first id and cp_finish_decomp walks DECL_CHAIN to find other ids.
> tsub
OK.
On Thu, Apr 5, 2018 at 5:06 PM, Jakub Jelinek wrote:
> Hi!
>
> We can't call maybe_apply_pragma_weak for structured binding decls
> at start_decl time, as that is too early, we don't have DECL_ASSEMBLER_NAME
> computed yet for them and because we don't have the corresponding decls
> around ye
Hi!
For cp_finish_decomp we require that the id decl for the structured binding
are chained together, because we pass just the artificial underlying decl
and first id and cp_finish_decomp walks DECL_CHAIN to find other ids.
tsubst_decomp_names was actually requiring not just that, but also that
th
Hi!
We can't call maybe_apply_pragma_weak for structured binding decls
at start_decl time, as that is too early, we don't have DECL_ASSEMBLER_NAME
computed yet for them and because we don't have the corresponding decls
around yet, we can't even compute it.
This patch defers the maybe_apply_pragma
The issue here was that check_array_designated_initializer did
constant folding to produce a constant index, but then left the
un-folded value behind to confuse complete_array_type. Fixed by
updating ce->value with the folded value. We should also use
fold_non_dependent_expr, and handle dependent
Hi!
As mentioned in the PR, on the following testcase we cp_save_expr in order
to avoid evaluating -1 * __builtin_expect (({ ... }), ...) twice and use
the SAVE_EXPR in the original shift as well as in a comparison, but then
we attempt to optimize the comparison by grabbing parts of the SAVE_EXPR,
On Thu, Apr 05, 2018 at 02:32:08PM +0200, Richard Biener wrote:
>
> This fixes exponential time spent in find_base_term by extending the
> existing fix of NULL-ifying VALUE locations during their processing
> to keep them NULL-ified during the whole recursion.
>
> As Jakub figured this has the ch
Since my patch for 69847 stopped us from giving a STRING_CST VLA type,
the check in process_init_constructor_array to make sure our
initializer has the right type breaks. Let's just adjust the sanity
check to look through arrays rather than try to be more specific.
Tested x86_64-pc-linux-gnu, app
"H.J. Lu" writes:
> config/
>
> * plugins.m4 (AC_PLUGINS): Use dlsym to check if libdl is needed.
This is OK.
On Thu, Apr 5, 2018 at 5:50 AM, Jakub Jelinek wrote:
> On Thu, Apr 05, 2018 at 09:45:54AM +, Segher Boessenkool wrote:
>> To find out where on-entry register values live at any point in a
>> program, GDB currently tries to parse to parse the executable code.
>> This does not work very well, fo
On 26 March 2018 at 14:10, Jonathan Wakely wrote:
> This makes it possible to use our std::variant with Clang, as well as
> some minor tweaks to avoid ADL (so the compiler doesn't waste time
> looking in associated namespaces) and adjust whitespace.
>
>* include/std/variant (__get): Qualify
Hello!
We have to prevent memory attribute calculation to access non-existent
operand[2] for rotate1 type insns in the same way as for ishift1 type
insns.
2018-04-05 Uros Bizjak
PR target/85193
* config/i386/i386.md (define_attr "memory"): Handle rotate1 type.
testsuite/ChangeLog:
2
Building a deduction guide for a constructor inherited from a
non-dependent base got confused because it has no template parameters.
Since there's no way an inherited constructor could be useful for
class template argument deduction, we can just skip them.
Tested x86_64-pc-linux-gnu, applying to
On 04/04/2018 07:44 PM, Martin Sebor wrote:
On 04/04/2018 05:50 PM, dave.pa...@oracle.com wrote:
On 04/04/2018 10:58 AM, Martin Sebor wrote:
On 04/04/2018 11:15 AM, Jakub Jelinek wrote:
On Tue, Apr 03, 2018 at 01:36:13PM -0600, Martin Sebor wrote:
On 04/03/2018 10:26 AM, dave.pa...@oracle.com
On 03/02/2018 09:47 PM, Cesar Philippidis wrote:
libgomp/
* plugin/plugin-nvptx.c (nvptx_exec): Adjust calculations of
workers and vectors.
I wrote a test case that triggers this code, and added it to this code.
Build x86_64 with nvptx accelerator and tested libgomp.
C
On 03/30/2018 05:14 PM, Tom de Vries wrote:
On 03/30/2018 05:00 PM, Cesar Philippidis wrote:
I should
have checked that patch with the vector length fallback disabled.
Right. The patch series introduces a lot of code that is not exercised.
I've added an -mlong-vector-in-workers option in my l
On 03/02/2018 08:18 PM, Cesar Philippidis wrote:
The attached patch adjusts the existing goacc validate_dims target hook
and introduces a new goacc adjust_parallelism target hook.
The attached patch now just introduces the nvptx_adjust_parallelism
target hook implementation, which enables test
On 03/02/2018 06:51 PM, Cesar Philippidis wrote:
This patch teaches the nvptx BE how to process vector reductions with
large vector lengths.
As with the "[nvptx] Generalize state propagation and synchronization"
patch":
- added use of MAX and ROUND_UP
- added missing initialization of vector_
Another place we need to use fold_non_dependent_expr so that constant
evaluation happens in non-template context.
Tested x86_64-pc-linux-gnu, applying to trunk.
commit 1f7ec60303854ae6c79034223aba5ad996b86843
Author: Jason Merrill
Date: Thu Apr 5 10:46:27 2018 -0400
PR c++/84665 -
On 05/04/18 16:13, Thomas Preudhomme wrote:
Hi Kyrill,
On 04/04/18 18:20, Thomas Preudhomme wrote:
Hi Kyrill,
On 04/04/18 18:19, Kyrill Tkachov wrote:
Hi Thomas,
On 04/04/18 18:03, Thomas Preudhomme wrote:
Hi,
__builtin_cmse_nonsecure_caller implementation returns true in almost
all cases
On Thu, Apr 05, 2018 at 09:53:41AM -0400, Jason Merrill wrote:
> OK.
Is this something that should go into cxx-status.html? Is that a DR,
applying to C++17 too?
> On Thu, Apr 5, 2018 at 5:06 AM, Ville Voutilainen
> wrote:
> > Tested on Linux-PPC64.
> >
> > 2018-04-05 Ville Voutilainen
> >
>
Hi Kyrill,
On 04/04/18 18:20, Thomas Preudhomme wrote:
Hi Kyrill,
On 04/04/18 18:19, Kyrill Tkachov wrote:
Hi Thomas,
On 04/04/18 18:03, Thomas Preudhomme wrote:
Hi,
__builtin_cmse_nonsecure_caller implementation returns true in almost
all cases due to 2 separate bugs:
* gen_addsi is used
Now that we instantiate lambdas with their enclosing context, the
closure type doesn't have CLASSTYPE_TEMPLATE_INFO.
Tested x86_64-pc-linux-gnu, applying to trunk.
commit 7c51c3a6ef0b137fc124ba65f686a607370f2c3a
Author: Jason Merrill
Date: Thu Apr 5 10:26:20 2018 -0400
PR c++/85228
On 04/05/2018 03:00 PM, Jakub Jelinek wrote:
> On Thu, Apr 05, 2018 at 02:51:22PM +0200, Martin Liška wrote:
>> On 04/04/2018 09:31 PM, Marek Polacek wrote:
>>> On Tue, Apr 03, 2018 at 02:29:37PM +0200, Martin Liška wrote:
Hi.
This helps the warning with --save-temps. Doing that one
On Thu, Apr 5, 2018 at 10:07 AM, Paolo Carlini wrote:
> Hi,
>
> On 05/04/2018 15:56, Jason Merrill wrote:
>>
>> On Thu, Apr 5, 2018 at 8:27 AM, Paolo Carlini
>> wrote:
>>>
>>> Hi,
>>>
>>> the main issue is already fixed in trunk but we still ICE on the reduced
>>> testcase attached by Jakub which
OK, thanks.
On Thu, Apr 5, 2018 at 10:06 AM, Ville Voutilainen
wrote:
> On 5 April 2018 at 16:37, Jason Merrill wrote:
>> On Wed, Apr 4, 2018 at 6:26 PM, Ville Voutilainen
>> wrote:
>>> + tree parm = TREE_VEC_ELT (TREE_VALUE (tparms), 0);
>>
>> I think you want to use INNERMOST_TEMPLATE_PARMS
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_stack_and_probe_stack_clash in
explow.c and passed down to gen_probe_stack
without any validation in emit_stack_probe
On Wed, Apr 4, 2018 at 2:57 PM, Jason Merrill wrote:
> Since, during partial instantiation of a generic lambda, we don't
> substitute into the body of a constexpr if, we don't do lambda capture
> as part of substitution. But extract_locals_r is supposed to do it as
> part of remembering the subst
On 04/04/2018 08:51 AM, Gerald Pfeifer wrote:
> On Tue, 3 Apr 2018, Martin Liška wrote:
>> I would like to document features I prepared in time frame of GCC 8.
>
> A few observations in addition what Martin (S.) provided (Thanks!):
>
> Index: htdocs/gcc-8/changes.html
> ==
On 04/03/2018 05:00 PM, Tom de Vries wrote:
+ unsigned int psize = ROUND_UP (data.offset, oacc_bcast_align);
+ unsigned int pnum = (nvptx_mach_vector_length () > PTX_WARP_SIZE
+ ? nvptx_mach_max_workers () + 1
+ : 1);
This claims too m
On 03/02/2018 06:51 PM, Cesar Philippidis wrote:
This patch teaches the nvptx BE how to process vector reductions with
large vector lengths.
Committed test-case exercising large vector length with reductions.
Thanks,
- Tom
[openacc] Add vector-length-128-10.c
2018-04-05 Tom de Vries
* te
Hi,
On 05/04/2018 15:56, Jason Merrill wrote:
On Thu, Apr 5, 2018 at 8:27 AM, Paolo Carlini wrote:
Hi,
the main issue is already fixed in trunk but we still ICE on the reduced
testcase attached by Jakub which has a broken std::initializer_list missing
the definition. I think we can handle thi
On 04/03/2018 05:00 PM, Tom de Vries wrote:
On 03/02/2018 05:55 PM, Cesar Philippidis wrote:
* config/nvptx/nvptx.c (oacc_bcast_partition): Declare.
One last thing: this variable needs to be reset to zero for every function.
Without this reset, we can generated different code for a functi
On 5 April 2018 at 16:37, Jason Merrill wrote:
> On Wed, Apr 4, 2018 at 6:26 PM, Ville Voutilainen
> wrote:
>> + tree parm = TREE_VEC_ELT (TREE_VALUE (tparms), 0);
>
> I think you want to use INNERMOST_TEMPLATE_PARMS here rather than
> TREE_VALUE directly.
>
> Please also add a comment quoting
On Thu, Apr 5, 2018 at 9:56 AM, Jakub Jelinek wrote:
> On Thu, Apr 05, 2018 at 09:53:41AM -0400, Jason Merrill wrote:
>> OK.
>
> Is this something that should go into cxx-status.html? Is that a DR,
> applying to C++17 too?
Probably, and yes.
>> On Thu, Apr 5, 2018 at 5:06 AM, Ville Voutilainen
On Thu, Apr 5, 2018 at 8:27 AM, Paolo Carlini wrote:
> Hi,
>
> the main issue is already fixed in trunk but we still ICE on the reduced
> testcase attached by Jakub which has a broken std::initializer_list missing
> the definition. I think we can handle this case similarly to the existing
> check
OK.
On Thu, Apr 5, 2018 at 5:06 AM, Ville Voutilainen
wrote:
> Tested on Linux-PPC64.
>
> 2018-04-05 Ville Voutilainen
>
> gcc/cp
>
> Implement P0969
> * decl.c (find_decomp_class_base): Check accessibility instead
> of declared access, adjust diagnostic.
>
> testsuite/
>
>
On Wed, Apr 4, 2018 at 8:48 PM, Paolo Carlini wrote:
> I'm really happy to report that these 5 ugly lines are causing an actual
> bug. Seriously, not considering the formatting, the problem is that we
> really want to keep 'type' in sync, because we are using it below before
> returning. Note that
On Wed, Apr 4, 2018 at 6:26 PM, Ville Voutilainen
wrote:
> + tree parm = TREE_VEC_ELT (TREE_VALUE (tparms), 0);
I think you want to use INNERMOST_TEMPLATE_PARMS here rather than
TREE_VALUE directly.
Please also add a comment quoting the rule you're implementing.
Jason
On Thu, Apr 05, 2018 at 05:08:36AM -0500, Segher Boessenkool wrote:
> On Thu, Apr 05, 2018 at 11:50:38AM +0200, Jakub Jelinek wrote:
> > On Thu, Apr 05, 2018 at 09:45:54AM +, Segher Boessenkool wrote:
> > > To find out where on-entry register values live at any point in a
> > > program, GDB cur
On Thu, Apr 05, 2018 at 02:51:22PM +0200, Martin Liška wrote:
> On 04/04/2018 09:31 PM, Marek Polacek wrote:
> > On Tue, Apr 03, 2018 at 02:29:37PM +0200, Martin Liška wrote:
> >> Hi.
> >>
> >> This helps the warning with --save-temps. Doing that one needs to preserve
> >> comments
> >> in preproc
On Wed, Apr 4, 2018 at 12:25 PM, Alexandre Oliva wrote:
> On Apr 4, 2018, Jason Merrill wrote:
>
>> On Tue, Apr 3, 2018 at 11:25 PM, Alexandre Oliva wrote:
>>> I still think we could attempt to retain the extension as it is, parsing
>>> types introduced in data member initializers within the sc
On 04/04/2018 09:31 PM, Marek Polacek wrote:
> On Tue, Apr 03, 2018 at 02:29:37PM +0200, Martin Liška wrote:
>> Hi.
>>
>> This helps the warning with --save-temps. Doing that one needs to preserve
>> comments
>> in preprocessed source file.
>
> Do we really want to only use -C when -Wimplicit-fal
This fixes exponential time spent in find_base_term by extending the
existing fix of NULL-ifying VALUE locations during their processing
to keep them NULL-ified during the whole recursion.
As Jakub figured this has the chance of returning NULL prematurely
for the case of the plus/minus case rejec
Hi All,
This patch fixes the code generation for copy_blkmode_to_reg by calculating
the bitsize per iteration doing the maximum copy allowed that does not read more
than the amount of bits left to copy.
This fixes the bad code generation reported and also still produces better code
in most cases.
Hi,
the main issue is already fixed in trunk but we still ICE on the reduced
testcase attached by Jakub which has a broken std::initializer_list
missing the definition. I think we can handle this case similarly to the
existing check in do_pushtag, which would be also consistent with the
plain
On Thu, Apr 05, 2018 at 09:45:54AM +, Segher Boessenkool wrote:
> To find out where on-entry register values live at any point in a
> program, GDB currently tries to parse to parse the executable code.
> This does not work very well, for example it gets confused if some
> accesses to the stack
On Thu, Apr 05, 2018 at 09:01:02AM +0200, Andreas Krebbel wrote:
> > Wouldn't it be better to just use aligned (8) and aligned (16) instead of
> > aligned (4) and aligned (8)?
>
> aligned (8) does not trigger the warning anymore. Neither on s390 nor on
> x86. I don't think there
> is a way to e
On Thu, Apr 05, 2018 at 11:50:38AM +0200, Jakub Jelinek wrote:
> On Thu, Apr 05, 2018 at 09:45:54AM +, Segher Boessenkool wrote:
> > To find out where on-entry register values live at any point in a
> > program, GDB currently tries to parse to parse the executable code.
> > This does not work v
To find out where on-entry register values live at any point in a
program, GDB currently tries to parse to parse the executable code.
This does not work very well, for example it gets confused if some
accesses to the stack use the frame pointer (r31) and some use the
stack pointer (r1). A symptom
Tested on Linux-PPC64.
2018-04-05 Ville Voutilainen
gcc/cp
Implement P0969
* decl.c (find_decomp_class_base): Check accessibility instead
of declared access, adjust diagnostic.
testsuite/
Implement P0969
* g++.dg/cpp1z/decomp4.C: Adjust.
* g++.dg/cpp1z/decomp
Hi,
When compiling the test-case in the patch, the following ptx code is
generated:
...
$L4:
@ %r91 bra.uni $L24;
selp.u32 %r95,1,0,%r80;
st.shared.u32 [__worker_bcast],%r95;
$L25:
$L24:
@ %r92 bra $L25;
...
There's an eternal loop starting at the last insn, and unsurprisingly
the t
Hi!
I'd like to ping the
http://gcc.gnu.org/ml/gcc-patches/2018-03/msg01244.html
- PR83157 - improve debug info for x86 setcc peepholes
patch. Thanks.
Jakub
On Wed, Apr 04, 2018 at 03:47:18PM -0500, Bill Schmidt wrote:
> > If we (for GCC9?) want to create a spot for target C++ tests, we should
> > just add g++.target// directories and add all the needed infrastructure
> > for those.
> >
> > Can you please revert the powerpc.exp change and move the tes
On Wed, 4 Apr 2018, Jakub Jelinek wrote:
> Hi!
>
> On the following testcase because of the SCCVN limit we end up with a weird,
> but valid, BIT_FIELD_REF - trying to extract V1TImode type out of a V1TImode
> SSA_NAME, with 128 bits width and offset 0 (just SSA_NAME move would be
> enough). Not
On 04/04/2018 07:34 PM, Jakub Jelinek wrote:
> On Wed, Apr 04, 2018 at 06:51:00PM +0200, Andreas Krebbel wrote:
>>> On targets enforcing a function alignment bigger than 4 bytes this triggers
>>> an error instead:
>>>
>>> +inline int ATTR ((aligned (4)))
>>> +finline_hot_noret_align (int); /* { d
60 matches
Mail list logo
