Hi Richard!
On Mon, 7 Nov 2016 13:19:21 +0100 (CET), Richard Biener
wrote:
> PR tree-optimization/78218
> --- gcc/testsuite/gcc.dg/torture/pr78218.c(revision 0)
> +++ gcc/testsuite/gcc.dg/torture/pr78218.c(working copy)
> @@ -0,0 +1,24 @@
> +/* { dg-do run } */
> +
> +struct
> +{
On Thu, Feb 16, 2017 at 8:41 PM, Bernd Schmidt wrote:
> We have two registers being assigned to each other:
>
> (set (reg 213) (reg 209))
> (set (reg 209) (reg 213))
>
> These being the only definitions, we are happy to forward propagate reg 209
> for reg 213 into a third insn, making a new use
On Fri, Feb 17, 2017 at 10:07 AM, Richard Biener
wrote:
> On Thu, Feb 16, 2017 at 8:41 PM, Bernd Schmidt wrote:
>> We have two registers being assigned to each other:
>>
>> (set (reg 213) (reg 209))
>> (set (reg 209) (reg 213))
>>
>> These being the only definitions, we are happy to forward pro
On Fri, 17 Feb 2017, Marek Polacek wrote:
> For "(int) -x", which is a NOP_EXPR, negate_expr_p returns true, which means
> that fold_negate_expr cannot return NULL_TREE. But that's what happens here,
> leading to a crash in fold_build2. negate_expr_p has (as well as negate_expr)
> STRIP_SIGN_NOP
On Fri, 17 Feb 2017, Thomas Schwinge wrote:
> Hi Richard!
>
> On Mon, 7 Nov 2016 13:19:21 +0100 (CET), Richard Biener
> wrote:
> > PR tree-optimization/78218
>
> > --- gcc/testsuite/gcc.dg/torture/pr78218.c (revision 0)
> > +++ gcc/testsuite/gcc.dg/torture/pr78218.c (working copy)
> > @@
Hi,
On Wed, Feb 08, 2017 at 01:49:17PM +0100, Jakub Jelinek wrote:
> On Wed, Feb 08, 2017 at 01:41:24PM +0100, Martin Jambor wrote:
> > 2017-02-08 Martin Jambor
> >
> > * common.opt (-finstrument-functions-exclude-file-list): Remove Var
> > and Optimization, Document as deprecated and
On Fri, Feb 17, 2017 at 10:31:16AM +0100, Martin Jambor wrote:
> @@ -8066,12 +8065,8 @@ This flag is enabled by default at @option{-O3}.
>
> @item -fipa-cp-alignment
> @opindex -fipa-cp-alignment
> -When enabled, this optimization propagates alignment of function
> -parameters to support better
On Thu, 16 Feb 2017, Richard Biener wrote:
>
> I am testing the following patch for PR79547. Those builtins do not
> return anything that can be used to re-construct the pointer(s) passed
> to them.
>
> Queued for GCC 8.
Actually we need calluse constraints. Thus adjusted as follows.
Richard
I am boostrapping the following to fix reported warnings about
bogus escape chars on mingw32 for genmatch output. Reporter
tested this on mingw.
Will commit after bootstrap on x86_64-unknown-linux-gnu finished
(well, somewhat pointless, DIR_SEPARATOR_2 is not defined there).
Richard.
2017-02-1
The following fixes PR79552 on trunk (for the branch it would also need
backporting of r235147 to not regress PR48885 - its fix caused this
regression).
Bootstrapped on x86_64-unknown-linux-gnu, testing in progress.
Richard.
2017-02-17 Richard Biener
PR tree-optimization/79552
posix_memalign is portable to older, non-c11 runtimes.
2017-02-17 Uros Bizjak
* gcc.dg/strncmp-2.c (test_driver_strncmp): Use posix_memalign
instead of aligned_alloc.
Tested on x86_64-linux-gnu, CentOS 5.11.
OK for mainline?
Uros.
diff --git a/gcc/testsuite/gcc.dg/strncmp-2.c b/gcc/
On 02/16/2017 12:34 PM, Richard Biener wrote:
> Yes, we should handle all of the "hidden initialized" cases at
>
> /* A PARM_DECL will not have an SSA_NAME_DEF_STMT. Parameters
> get their initial value from function entry. */
> if (SSA_NAME_VAR (t) && TREE_CODE (SSA_NAME_VA
On Fri, Feb 17, 2017 at 3:40 AM, Jeff Law wrote:
> On 02/14/2017 03:05 AM, Bin Cheng wrote:
>>
>> Hi,
>> This is the second try fixing PR71437. The old version patch tried to fix
>> issue in VRP but it requires further non-trivial change in VRP,
>> specifically, to better support variable value r
On Fri, Feb 17, 2017 at 10:55 AM, Martin Liška wrote:
> On 02/16/2017 12:34 PM, Richard Biener wrote:
>> Yes, we should handle all of the "hidden initialized" cases at
>>
>> /* A PARM_DECL will not have an SSA_NAME_DEF_STMT. Parameters
>> get their initial value from function entry
On Fri, 17 Feb 2017, Richard Biener wrote:
On Thu, 16 Feb 2017, Richard Biener wrote:
I am testing the following patch for PR79547. Those builtins do not
return anything that can be used to re-construct the pointer(s) passed
to them.
Queued for GCC 8.
Actually we need calluse constraints.
On 02/14/2017 10:42 AM, JonY wrote:
> On 02/14/2017 09:32 AM, Thomas Preudhomme wrote:
>>>
>>> Looks good, be sure to emphasize this option affects mingw hosted GCC
>>> only, not the compiler output.
>>
>> I think that should be pretty clear in the latest version of the patch,
>> doc/install.texi c
On Fri, 17 Feb 2017, Marc Glisse wrote:
> On Fri, 17 Feb 2017, Richard Biener wrote:
>
> > On Thu, 16 Feb 2017, Richard Biener wrote:
> >
> > >
> > > I am testing the following patch for PR79547. Those builtins do not
> > > return anything that can be used to re-construct the pointer(s) passed
Here you are:
2017-01-24 Thomas Preud'homme
* configure.ac (--enable-mingw-wildcard): Add new configurable feature.
* configure: Regenerate.
* config.in: Regenerate.
* config/i386/driver-mingw32.c: new file.
* config/i386/x-mingw32: Add rule to build dr
The following annotates two key wrappers around copy_node in the C++ FE
with MEM-STAT info (and with CXX_MEM_STAT_INFO this is surprisingly
easy, without adding _stat variants and macros as we have for the classic
way from the pre-C++ era).
It also annotates more type building functions in tree.c
On Fri, 17 Feb 2017, Richard Biener wrote:
>
> The following annotates two key wrappers around copy_node in the C++ FE
> with MEM-STAT info (and with CXX_MEM_STAT_INFO this is surprisingly
> easy, without adding _stat variants and macros as we have for the classic
> way from the pre-C++ era).
>
On Fri, Feb 17, 2017 at 01:22:57PM +0100, Richard Biener wrote:
> And even unify CXX_MEM_STAT_INFO and MEM_STAT_INFO, also dropping support
> for host compilers < GCC 4.8, GCC 4.8 introduced __builtin_FILE and
> friends (you'd have to bootstrap with older host compilers or clang
> which doesn't see
On Thu, Feb 16, 2017 at 11:56 PM, Koval, Julia wrote:
> Sorry, here is the right patch(previous one had a typo). Changelog is right.
>
>
> -Original Message-
> From: Koval, Julia
> Sent: Thursday, February 16, 2017 11:31 PM
> To: 'Uros Bizjak'
> Cc: GCC Patches
> Subject: RE: [PATCH] Ena
On Fri, 17 Feb 2017, Jakub Jelinek wrote:
> On Fri, Feb 17, 2017 at 01:22:57PM +0100, Richard Biener wrote:
> > And even unify CXX_MEM_STAT_INFO and MEM_STAT_INFO, also dropping support
> > for host compilers < GCC 4.8, GCC 4.8 introduced __builtin_FILE and
> > friends (you'd have to bootstrap wit
Currently there's no way to disable the warning about literal suffix
identifiers that use reserved names. This patch from Eric makes it
depend on the existing -Wliteral-suffix option. Currently that
controls warnings when encountering string literals concatenated with
macros, such as "%"PRIu32, wh
Hi,
For the following test-case:
int __GIMPLE () foo (int a)
{
return t0_1(D);
}
The compiler emits the undeclared diagnostic and then ICE's in
c_parser_gimple_postfix_expression because we don't check if
c_parser_parse_ssa_name returned error_mark_node.
ICE: https://gist.github.com/anonymous/4
Hi!
On Fri, 17 Feb 2017 14:00:09 +0100, I wrote:
> [...] for "normal" functions there is no reason to use the
> ".param" space for passing arguments in and out of functions. We can
> then get rid of the boilerplate code to move ".param %in_ar*" into ".reg
> %ar*", and the other way round for "%va
Hi,
Can you please commit it for me?
Thanks,
Julia
-Original Message-
From: Uros Bizjak [mailto:ubiz...@gmail.com]
Sent: Friday, February 17, 2017 1:30 PM
To: Koval, Julia
Cc: GCC Patches
Subject: Re: [PATCH] Enable RDPID instruction.
On Thu, Feb 16, 2017 at 11:56 PM, Koval, Julia wr
Hi,
this ICE on invalid seems quite similar to c++/69637 which I fixed
recently: we again end up with an unhandled OVERLOAD in the main
cxx_eval_constant_expression switch and in this case we don't diagnose
at all the invalid input. Thus, I propose to add a check to
cxx_alignas_expr completel
On Fri, 17 Feb 2017, Prathamesh Kulkarni wrote:
> Hi,
> For the following test-case:
>
> int __GIMPLE () foo (int a)
> {
> return t0_1(D);
> }
>
> The compiler emits the undeclared diagnostic and then ICE's in
> c_parser_gimple_postfix_expression because we don't check if
> c_parser_parse_ssa_
... sorry, what I meant to propose uses
INTEGRAL_OR_UNSCOPED_ENUMERATION_TYPE_P in the check, per the below.
Both versions pass testing anyway, but the below seems more correct to me.
Thanks again,
Paolo.
Index: cp/typeck.c
=
The following fixes too deep recursion with insane
--param max-ssa-name-query-depth by limiting the param appropriately.
Given the search is not width limited it can be highly exponential
in complexity thus I limited it fairly low (10).
Committed as obvious.
Richard.
2017-02-17 Richard Biener
We are crashing with a label as a value without accompanying goto.
The problem is that TREE_SIDE_EFFECTS and FORCED_LABEL use the same
->base.side_effects_flag, so gimplify_expr is confused. We don't
ICE with 'goto *&&L;' becase then we take this path:
11406 case GOTO_EXPR:
11407
The old copy elision code in build_over_call checks to make sure that
we don't hit it for a temporary object in C++17, where it should have
been handled at a higher level. We were hitting it for this testcase
because the compiler was looking through the cast to reference type to
find the temporary
Hello.
Increasing minimum of param fixes the issue. I guess 0 as value does not makes
any
real sense.
Ready for trunk?
Thanks,
Martin
>From 84f39f731373a8b2703569ac23080b8278539ea9 Mon Sep 17 00:00:00 2001
From: marxin
Date: Fri, 17 Feb 2017 15:03:22 +0100
Subject: [PATCH] Increase minimum for
Hi.
Following patch prevents integer overflow with a huge param.
Patch can bootstrap on ppc64le-redhat-linux and survives regression tests.
Ready to be installed?
Martin
>From c92bbded326bb117d6c5bfcb1f505f2bbffc0b75 Mon Sep 17 00:00:00 2001
From: marxin
Date: Fri, 17 Feb 2017 13:46:21 +0100
Su
On Fri, Feb 17, 2017 at 3:17 PM, Martin Liška wrote:
> Hello.
>
> Increasing minimum of param fixes the issue. I guess 0 as value does not
> makes any
> real sense.
>
> Ready for trunk?
Ok.
Richard.
> Thanks,
> Martin
On Fri, Feb 17, 2017 at 3:18 PM, Martin Liška wrote:
> Hi.
>
> Following patch prevents integer overflow with a huge param.
>
> Patch can bootstrap on ppc64le-redhat-linux and survives regression tests.
>
> Ready to be installed?
Ok.
Richard.
> Martin
A cast from float to double should turn a signaling NaN into a quiet
NaN, if using -fsignaling-nans. On PowerPC single-precision floats are
stored as double precision in registers, and so, the cast normally does
nothing. This causes gcc.dg/pr59833.c to fail (it does such a cast,
and expects a qui
Hello.
We should not have a default value (different from -1) that is smaller than
minimum.
Ready to be installed after tests?
Martin
>From 4ea71d245bda258ebaed22cb3661fff0265c7088 Mon Sep 17 00:00:00 2001
From: marxin
Date: Fri, 17 Feb 2017 16:00:30 +0100
Subject: [PATCH] Change default of par
Hi Bill,
On Thu, Feb 16, 2017 at 02:16:02PM -0600, Bill Schmidt wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79261 records that the interface
> vec_xxpermdi isn't implemented in a bi-endian fashion; instead, it produces
> results appropriate for big-endian vector element numbering even wh
On 16.02.17 22:20, Andreas Tobler wrote:
On 16.02.17 22:03, Jakub Jelinek wrote:
On Thu, Feb 16, 2017 at 09:57:48PM +0100, Andreas Tobler wrote:
is this patch ok for trunk?
Fixes bootstrap for x86_64-*-freebsd12 where the internal struct rtentry has
gone from userland.
TIA,
Andreas
2017-02-1
On Fri, Feb 17, 2017 at 07:24:45AM +0100, Andreas Tobler wrote:
> > Yeah, I understand. This is due to the fact that on FreeBSD trunk (aka.
> > *-*-freebsd12) this commit
> > (https://svnweb.freebsd.org/base?view=revision&revision=313560) dropped
> > the _WANT_RTENTRY from net/route.h.
> > Iow, all
This patch to libgo updates the sources to the final Go 1.8 release.
Along with the update this fixes a problem that was always present but
only showed up with a new test in the reflect package. When a program
used a **unsafe.Pointer and stored the value in an interface type, the
generated type d
The following patch fixes
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79541
The patch was successfully bootstrapped and tested on x86-64.
Committed as rev. 245536.
Index: ChangeLog
===
--- ChangeLog (revision 245535)
+++ ChangeL
On Sun, May 29, 2016 at 11:10:15PM +0200, Uros Bizjak wrote:
> As explained in PR71245, comment #3 [1], it is better to use offset -4
> to a %esp to implement a non-SSE memory fence instruction:
>
> -q-
>
> I guess it costs a code byte for a disp8 in the addressing mode, but
> it avoids adding a
GCC Maintainers:
Here is the GCC 6 branch back port of the mainline fixes for the RTL
definitions for xvcvsxdsp and xvcvuxdsp instructions, commit r245460 on
2017-02-14. The GCC 5 backport of these fixes have already been
approved and committed.
The RTL defined the instructions with a V2DF argu
Hi,
Thanks for all the feedback. Hopefully it's all incorporated now.
I will reply to you individually on the specific topics, but here is
the new v6 for you to rip apart ;-)
Changes since v5:
* ChangeLogs split, reshuffled, reformatted.
* cmdline option parsing again with integral_argument ()
On Fri, Feb 17, 2017 at 5:30 PM, Jakub Jelinek wrote:
> On Sun, May 29, 2016 at 11:10:15PM +0200, Uros Bizjak wrote:
>> As explained in PR71245, comment #3 [1], it is better to use offset -4
>> to a %esp to implement a non-SSE memory fence instruction:
>>
>> -q-
>>
>> I guess it costs a code byte
On Fri, Feb 17, 2017 at 05:59:30PM +0100, Uros Bizjak wrote:
> > Unfortunately this makes valgrind unhappy about that:
> > https://bugzilla.redhat.com/show_bug.cgi?id=1423434
> > I assume it will complain now on anything pre-SSE2 that contains the memory
> > barrier in 32-bit code.
> > Perhaps we s
On Wed, Feb 15, 2017 at 11:01:16AM +, Richard Earnshaw (lists) wrote:
> On 13/01/17 12:19, Torsten Duwe wrote:
>
> > +++ b/gcc/doc/invoke.texi
> > @@ -11341,6 +11341,27 @@ of the function name, it is considered to be a
> > match. For C99 and C++
> > extended identifiers, the function name m
On Wed, Feb 08, 2017 at 12:48:56PM +0100, Jakub Jelinek wrote:
>
> First of all, GCC is in stage4 and this isn't a fix for a regression, so it
> is not acceptable at this point. Next stage1 will start in April or so.
I had gotten the impression there were sort of branches in the SCM; this
of cou
Hi!
Asserts don't work really well on something we can't control in inline asm.
output_operand_lossage takes care to ICE outside of inline asm and error out
inside inline asm.
Bootstrapped/regtested on x86_64-linux and i686-linux, ok for trunk?
2017-02-17 Jakub Jelinek
PR target/7955
Hi!
-m3dnowa is an undocumented option that always errors out.
The following patch fixes it and makes it do the obvious thing.
Bootstrapped/regtested on x86_64-linux and i686-linux, ok for trunk?
2017-02-17 Jakub Jelinek
PR target/79569
* config/i386/i386.opt (m3dnowa): Repla
In 79556, we try to deduce an auto type from a dependent initializer
with null TREE_TYPE, which doesn't work; fixed by catching that case
in do_auto_deduction.
In 79549, we try to tsubst into the type of a NONTYPE_ARGUMENT_PACK,
which doesn't make sense for an auto parameter pack; in fact, it
does
Hi!
The masks for builtins seems to be quite messy. Most of
the builtins have a single OPTION_MASK_ISA_* in there and that is
clear (i.e. that the builtin is only enabled/usable if that isa
bit is on). Then we have 0 and that is meant for always enabled builtins.
Then there is OPTION_MASK_ISA_xx
Hi!
DWARF5 that has been released recently had a fairly late change where
it says that C++ static data members should use DW_TAG_variable tag
instead of DW_TAG_member inside of the class DIE.
The following patch implements just that, not any further changes e.g.
to inline static data members (i.e
Hi!
The GDB folks expressed interest in handling column information in
debug info, apparently clang emits it, but gcc does not.
I know we are late in the release cycle, so I'm not suggesting to
turn this on by default, but the following patch at least allows
users to request it through -gcolumn-i
Hi!
And here is incremental patch to provide column information even in
.debug_line (whether through .loc directives or custom .debug_line).
The patch looks large, because I had to adjust the two hooks to pass
through the column information, but beyond that it is actually very simple.
If the earl
On 02/17/2017 05:09 AM, Thomas Schwinge wrote:
> On Fri, 17 Feb 2017 14:00:09 +0100, I wrote:
>> [...] for "normal" functions there is no reason to use the
>> ".param" space for passing arguments in and out of functions. We can
>> then get rid of the boilerplate code to move ".param %in_ar*" into
On 02/15/2017 01:29 PM, Thomas Schwinge wrote:
> On Mon, 13 Feb 2017 08:58:39 -0800, Cesar Philippidis
> wrote:
>> @@ -952,25 +958,30 @@ nvptx_exec (void (*fn), size_t mapnum, void
>> **hostaddrs, void **devaddrs,
>>CUdevice dev = nvptx_thread()->ptx_dev->dev;
>>/* 32 is the def
On 02/08/2017 08:00 AM, Paul Richard Thomas wrote:
Dear All,
The attached rework of the patch functions in the same way as
yesterday's but is based in resolve.c rather than trans-decl.c. It
looks to me to be by far cleaner.
Bootstraps and regtests on FC23/x86_64 - OK for trunk?
Cheers
Paul
2
We entered type_dependent_object_expression_p considering an
IDENTIFIER_NODE, which is always dependent. But because there's a
global type with the same name, the identifier had global_type_node as
its type, which isn't recognized as a dependent type. Fixed by
handling IDENTIFIER_NODE directly.
On Fri, Feb 17, 2017 at 08:30:26AM -0800, Carl E. Love wrote:
> The patch has been tested on powerpc64le-unknown-linux-gnu (Power 8 LE)
> with no regressions.
>
> Is the patch OK for gcc 6 branch?
Yes, thanks. In the future, please do 6 before 5.
Segher
This patch amends a patch merged with the trunk on 2017-01-14. One of
the new test cases added at that time has proven to be unreliable so
this path removes it.
Is this patch ok for trunk?
gcc/testsuite/ChangeLog:
2017-02-17 Kelvin Nilsen
PR target/78056
* gcc.target/powerp
My patch to limit template lookup after -> and . to class templates
sets parser->context->object_type even for a dependent object
expression, so that we know that there was one. This is normally
cleared in cp_parser_lookup_name, but cp_parser_template_name was
optimizing away the call to that func
On Fri, Feb 17, 2017 at 02:54:07PM -0700, Kelvin Nilsen wrote:
> This patch amends a patch merged with the trunk on 2017-01-14. One of
> the new test cases added at that time has proven to be unreliable so
> this path removes it.
In what way is it unreliable? What fails?
Segher
On Fri, Feb 17, 2017 at 02:54:07PM -0700, Kelvin Nilsen wrote:
> This patch amends a patch merged with the trunk on 2017-01-14. One of
> the new test cases added at that time has proven to be unreliable so
> this path removes it.
>
> Is this patch ok for trunk?
Okay, so the testcase just does no
On 02/17/2017 11:31 AM, Thomas Preudhomme wrote:
> Here you are:
>
> 2017-01-24 Thomas Preud'homme
>
> * configure.ac (--enable-mingw-wildcard): Add new configurable
> feature.
> * configure: Regenerate.
> * config.in: Regenerate.
> * config/i386/driver-mingw32.
By extending the set of floating types, TS 18661-3 thereby affected
the definition of DECIMAL_DIG, which is defined in terms of the
"widest supported floating type". This is not conditional on whether
__STDC_WANT_IEC_60559_TYPES_EXT__ is defined when is
included.
I raised this possible incompati
On 02/06/17 10:44, Bernd Edlinger wrote:
> I tested this change with different arm-linux-gnueabihf cross
> compilers, and verified that mkheaders still works on the host system.
>
> Bootstrapped and reg-tested on x86_64-pc-linux-gnu.
> Is it OK for trunk?
As long as you certify that this is corre
The attached patch fixes bug 79548 - [5/6/7 Regression] missing
-Wunused-variable on a typedef'd variable in a function template,
most likely broken by the introduction of -Wunused-local-typedefs.
While testing the patch I came across a couple of other bugs:
79585 - spurious -Wunused-variable
OK.
On Fri, Feb 17, 2017 at 1:57 PM, Jakub Jelinek wrote:
> Hi!
>
> The GDB folks expressed interest in handling column information in
> debug info, apparently clang emits it, but gcc does not.
>
> I know we are late in the release cycle, so I'm not suggesting to
> turn this on by default, but th
Looks fine.
On Fri, Feb 17, 2017 at 1:59 PM, Jakub Jelinek wrote:
> Hi!
>
> And here is incremental patch to provide column information even in
> .debug_line (whether through .loc directives or custom .debug_line).
> The patch looks large, because I had to adjust the two hooks to pass
> through t
On Fri, Feb 17, 2017 at 1:52 PM, Jakub Jelinek wrote:
> - && die->die_tag != DW_TAG_member)
> + && die->die_tag != DW_TAG_member
> + && (die->die_tag != DW_TAG_variable || !class_scope_p
> (die->die_parent)))
How about we only check class_scope_p (die->die_parent), and don't
consi
OK.
On Fri, Feb 17, 2017 at 8:32 AM, Paolo Carlini wrote:
> ... sorry, what I meant to propose uses
> INTEGRAL_OR_UNSCOPED_ENUMERATION_TYPE_P in the check, per the below. Both
> versions pass testing anyway, but the below seems more correct to me.
>
> Thanks again,
> Paolo.
>
> //
OK.
On Fri, Feb 17, 2017 at 7:59 AM, Jonathan Wakely wrote:
> Currently there's no way to disable the warning about literal suffix
> identifiers that use reserved names. This patch from Eric makes it
> depend on the existing -Wliteral-suffix option. Currently that
> controls warnings when encount
On Fri, Feb 17, 2017 at 6:51 AM, Richard Biener wrote:
>
> The following annotates two key wrappers around copy_node in the C++ FE
> with MEM-STAT info (and with CXX_MEM_STAT_INFO this is surprisingly
> easy, without adding _stat variants and macros as we have for the classic
> way from the pre-C+
On Thu, Feb 16, 2017 at 6:13 PM, Martin Sebor wrote:
> On 02/16/2017 12:49 PM, Jason Merrill wrote:
>>
>> On Thu, Feb 16, 2017 at 11:33 AM, Jakub Jelinek wrote:
>>>
>>> PR c++/79502
>>> * pt.c (apply_late_template_attributes): If there are
>>> no dependent attributes, set
On Fri, 17 Feb 2017, Cesar Philippidis wrote:
> > And then, I don't specifically have a problem with discontinuing CUDA 5.5
> > support, and require 6.5, for example, but that should be a conscious
> > decision.
>
> We should probably ditch CUDA 5.5. In fact, according to trunk's cuda.h,
> it requ
On 02/17/2017 09:57 AM, Torsten Duwe wrote:
diff --git a/gcc/doc/extend.texi b/gcc/doc/extend.texi
index 3d1546a..ef7e985 100644
--- a/gcc/doc/extend.texi
+++ b/gcc/doc/extend.texi
@@ -3076,6 +3076,23 @@ that affect more than one function.
This attribute should be used for debugging purposes o
80 matches
Mail list logo
