Re: [RFC][PATCH][mid-end] Optimize immediate choice in comparisons.

On 08/07/2018 02:11 PM, Richard Sandiford wrote: > Hi Vlad, > > Thanks for the patch. > > Vlad Lazar writes: >> Hi. >> >> This patch optimises the choice of immediates in integer comparisons. Integer >> comparisons allow for different choices (e.g. a > b is equivalent to a >= >> b+1) >> and

Re: [PATCH] Make strlen range computations more conservative

On 08/02/2018 09:42 AM, Martin Sebor wrote: > The warning bits are definitely not okay by me.  The purpose > of the warnings (-W{format,sprintf}-{overflow,truncation} is > to detect buffer overflows.  When a warning doesn't have access > to string length information for dynamically created

Re: [PATCH] Make strlen range computations more conservative

On 07/24/2018 05:18 PM, Bernd Edlinger wrote: > On 07/24/18 23:46, Jeff Law wrote: >> On 07/24/2018 01:59 AM, Bernd Edlinger wrote: >>> Hi! >>> >>> This patch makes strlen range computations more conservative. >>> >>> Firstly if there is a visible type cast from type A to B before passing >>> then

Re: [RFC,PATCH] Introduce -msdata=explicit for powerpc

On Aug 7, 2018, Segher Boessenkool wrote: > The approach looks like it should work, but it does not seem all that > convenient to me. And there's more, it's actually redundant. -msdata -G 0 is equivalent to the proposed -msdata=explicit. Patch withdrawn. Sorry about the noise. -- Alexandre

Re: [PATCH v2 01/10] Initial TI PRU GCC port

On Tuesday, 7 Aug 2018, 16:56:16 EEST Sandra Loosemore wrote: > > * doc/extend.texi: Document PRU pragmas. > > * doc/invoke.texi: Document PRU-specific options. > > * doc/md.texi: Document PRU asm constraints. > > I have a few nit-picky comments about the documentation parts. Thank you for the

Re: [PATCH] libstdc++-v3: Have aligned_alloc() on Newlib

On 08/08/18 16:33, Jonathan Wakely wrote: On 08/08/18 16:22 +0200, Ulrich Weigand wrote: Jonathan Wakely wrote: Aha, so newlib was using memalign previously: @@ -53,20 +54,24 @@ aligned_alloc (std::size_t al, std::size_t sz)  #else  extern "C" void *memalign(std::size_t boundary, std::size_t

Re: [PATCH] assume sprintf formatting of wide characters may fail (PR 86853)

On 08/04/2018 12:46 PM, Martin Sebor wrote: > The sprintf handling of wide characters neglects to consider > that calling the function may fail due to a conversion error > (when the wide character is invalid or not representable in > the current locale).  The handling also misinterprets > the 

[Bug tree-optimization/86889] s390x gcc build fails when configured with --disable-checking

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86889 Martin Sebor changed: What|Removed |Added Keywords||diagnostic CC|

Re: [llvm-dev] GCC 5 and -Wstrict-aliasing in JSON.h

Hi Kim, Thanks for your report! My GCC 4.9.3 is *not* able to reproduce the issue with reduced testcase[1] But it is able to reproduce the issue by compiling LLVM with GCC toolchain[2] In file included from /home/loongson/llvm/lib/Support/JSON.cpp:10:0:

[Bug c/82967] "did you mean" suggestions are way too suggestive

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82967 Eric Gallager changed: What|Removed |Added Status|NEW |ASSIGNED See Also|

[Bug c++/86503] Segmentation fault signal terminated

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86503 --- Comment #3 from zhonghao at pku dot org.cn --- (In reply to Richard Biener from comment #1) > You run out of memory or stack. Try ulimit -s unlimited I tried ulimit -s unlimited. This time, the error messages are as follows: g++

[Bug c/86894] New: error for a zero-length array initialized with empty braced list

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86894 Bug ID: 86894 Summary: error for a zero-length array initialized with empty braced list Product: gcc Version: 9.0 Status: UNCONFIRMED Severity: normal

Re: [PATCH] convert braced initializers to strings (PR 71625)

On 08/08/2018 02:48 PM, Joseph Myers wrote: On Wed, 8 Aug 2018, Martin Sebor wrote: Jason/Joseph, is this meant to be accepted? It's rejected with a hard error with -Wpedantic but I don't see any tests for it: warning: ISO C forbids empty initializer braces [-Wpedantic] const char x[] = {

Re: [PATCH] convert braced initializers to strings (PR 71625)

On 08/08/2018 05:08 AM, Jason Merrill wrote: On Wed, Aug 8, 2018 at 9:04 AM, Martin Sebor wrote: On 08/07/2018 02:57 AM, Jason Merrill wrote: On Wed, Aug 1, 2018 at 12:49 AM, Martin Sebor wrote: On 07/31/2018 07:38 AM, Jason Merrill wrote: On Tue, Jul 31, 2018 at 9:51 AM, Martin Sebor

gcc-6-20180808 is now available

Snapshot gcc-6-20180808 is now available on ftp://gcc.gnu.org/pub/gcc/snapshots/6-20180808/ and on various mirrors, see http://gcc.gnu.org/mirrors.html for details. This snapshot has been generated from the GCC 6 SVN branch with the following options: svn://gcc.gnu.org/svn/gcc/branches/gcc-6

[Bug target/86772] [meta-bug] tracking port status for CVE-2017-5753

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86772 Andrew Pinski changed: What|Removed |Added Status|UNCONFIRMED |NEW Last reconfirmed|

[Bug rtl-optimization/86892] RTL CSE commoning trivial constants across call and/or too early

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86892 Segher Boessenkool changed: What|Removed |Added Status|UNCONFIRMED |NEW Last reconfirmed|

Re: [PATCH] convert braced initializers to strings (PR 71625)

On Wed, 8 Aug 2018, Martin Sebor wrote: > Jason/Joseph, is this meant to be accepted? It's rejected with > a hard error with -Wpedantic but I don't see any tests for it: > > warning: ISO C forbids empty initializer braces [-Wpedantic] >const char x[] = { }; > ^ > error:

Re: Ping for STRING_CST patches

On Wed, 8 Aug 2018, Bernd Edlinger wrote: > [PATCH] Handle overlength strings in the C FE > https://gcc.gnu.org/ml/gcc-patches/2018-08/msg00142.html At least this one had at least one review comment . -- Joseph S. Myers

[Bug rtl-optimization/86882] [9 Regression] ICE in reg_overlap_mentioned_p, at rtlanal.c:1873

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86882 --- Comment #5 from Segher Boessenkool --- So what is wrong about that? CONST_INTs are sign-extended always, so 0xff00 is just fine?

Re: [PATCH] convert braced initializers to strings (PR 71625)

On 08/08/18 21:50, Martin Sebor wrote: >> Sorry, again, but could it be possible that this test case changed >> with your patch? >> >> $ cat w.c >> const char  x[] = {  }; >> int main() >> { >>    __builtin_printf("%ld\n", sizeof(x)); >>    return 0; >> } >> $ gcc w.c >> $ ./a.out >> 1 >> >>

m68k: handle more cases of TLS symbols with offset

This is a better fix for PR target/46179. There are more DImode insns that call adjust_operand during output processing. Instead of scanning the insns in the FINAL_PRESCAN_INSN hook, adjust them directly before they are output by print_operand or print_operand_address. Andreas. PR

[Bug target/46179] Codegen/TLS: invalid assembler syntax

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=46179 --- Comment #13 from Andreas Schwab --- Author: schwab Date: Wed Aug 8 20:01:26 2018 New Revision: 263432 URL: https://gcc.gnu.org/viewcvs?rev=263432=gcc=rev Log: m68k: handle more cases of TLS symbols with offset PR target/46179 *

Re: [PATCH] Add sinh(tanh(x)) and cosh(tanh(x)) rules

Thanks. Ok, so the expressions you gave are undefined for x==1, which says that substituting something that is also undefined for x==1 is permitted. You can argue from "undefined" rather than relying on IEEE features like NaN or infinite. paul > On Aug 8, 2018, at 2:57 PM, Giuliano

Re: [PATCH] convert braced initializers to strings (PR 71625)

Sorry, again, but could it be possible that this test case changed with your patch? $ cat w.c const char x[] = { }; int main() { __builtin_printf("%ld\n", sizeof(x)); return 0; } $ gcc w.c $ ./a.out 1 without your patch $ ./a.out 0 Jason/Joseph, is this meant to be accepted? It's

[Bug fortran/86893] New: implement F202x .andthen. / .orelse. operators

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86893 Bug ID: 86893 Summary: implement F202x .andthen. / .orelse. operators Product: gcc Version: 9.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component:

Re: [PATCH] Add sinh(tanh(x)) and cosh(tanh(x)) rules

Sorry about that. In the e-mail text field I wrote sinh(tanh(x)) and cosh(tanh(x)) where it was supposed to be sinh(atanh(x)) and cosh(atanh(x)), thus I am talking about the inverse hyperbolic tangent function. The patch code and comments are still correct. On Wed, Aug 8, 2018 at 10:58 AM, Paul

[Bug target/82418] Division on a constant is suboptimal because of not using imul instruction

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82418 --- Comment #7 from Uroš Bizjak --- (In reply to Alexander Monakov from comment #6) > +;; Widest single word integer modes. > +(define_mode_iterator SWI48W [(SI "!TARGET_64BIT") > + (DI "TARGET_64BIT")]) Please use

Re: [PATCH] convert braced initializers to strings (PR 71625)

On 08/08/18 19:33, Bernd Edlinger wrote: > Hi Martin, > > sorry, I hope you forgive me, when I add a few comments to your patch. > >> +  unsigned HOST_WIDE_INT nelts = CONSTRUCTOR_NELTS (ctor); >> +  tree eltype = TREE_TYPE (type); > ... >> +  /* Bail if the CTOR has a block of more than 256

Re: Pool & Spa Constructors List

Eh, eh, the word pool can be a bit tricky with, say, memory allocators, but spam-filtering out messages containing the word spa seems pretty safe to me ;) Paolo.

[Bug target/82418] Division on a constant is suboptimal because of not using imul instruction

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82418 Alexander Monakov changed: What|Removed |Added CC||uros at gcc dot gnu.org --- Comment

Pool & Spa Constructors List

Hi, I would like to know if you are interested in acquiring the Contact List of Designers & Constructors of Pool & Spa for business campaign. Other Contact Lists: * Pool & Spa product retailers * Building Management Professionals * Villa design institutes, Decoration & Design

[Bug target/86651] [8/9 Regression] lto-wrapper.exe: fatal error: simple_object_copy_lto_debug_sections not implemented: Invalid argument

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86651 --- Comment #17 from jwjagersma at gmail dot com --- If anyone opens a new PR, please cc me. I am unable to contribute right now due to some health issues.

Re: [PATCH] line-map include-from representation

On 08/08/2018 11:36 AM, David Malcolm wrote: In r255786 I adjusted prune.exp to move the dg-regexp handling to before the pruning. Unfortunately, handle-multiline-outputs is still after the pruning. I guess we could try moving that to before as well, but I suspect it might break some things.

Re: [PATCH] convert braced initializers to strings (PR 71625)

Hi Martin, sorry, I hope you forgive me, when I add a few comments to your patch. > + unsigned HOST_WIDE_INT nelts = CONSTRUCTOR_NELTS (ctor); > + tree eltype = TREE_TYPE (type); ... > + /* Bail if the CTOR has a block of more than 256 embedded nuls > +due to implicitly

Re: [PATCH] Make strlen range computations more conservative

On August 8, 2018 5:51:16 PM GMT+02:00, Martin Sebor wrote: >On 08/07/2018 11:46 AM, Richard Biener wrote: >> On August 7, 2018 6:31:36 PM GMT+02:00, Martin Sebor > wrote: >>> On 08/07/2018 09:33 AM, Bernd Edlinger wrote: On 08/07/18 17:02, Martin Sebor wrote: > On 08/06/2018 11:45 PM,

[Bug rtl-optimization/86892] New: RTL CSE commoning trivial constants across call and/or too early

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86892 Bug ID: 86892 Summary: RTL CSE commoning trivial constants across call and/or too early Product: gcc Version: 9.0 Status: UNCONFIRMED Severity: normal

[Bug tree-optimization/86891] New: [9 Regression] wrong code with -O -frerun-cse-after-loop -fno-tree-dominator-opts -fno-tree-fre

ead model: posix gcc version 9.0.0 20180808 (experimental) (GCC) The generated code: main: stp x29, x30, [sp, -32]!//,,, mov x29, sp //, // testcase.c:11: u32 d = 7; mov w0, 7 // tmp106, str w0, [sp, 28]// tmp106, d // testcase.c:12:

Re: dejagnu version update?

On Wed, Aug 08, 2018 at 01:17:49PM +0200, Bernhard Reutner-Fischer wrote: > On 7 August 2018 18:34:30 CEST, Segher Boessenkool > wrote: > >On Mon, Aug 06, 2018 at 08:25:49AM -0700, Mike Stump wrote: > >> Since g++ already requires 1.5.3, it make no sense to bump to > >anything older that 1.5.3,

Re: dejagnu version update?

On Wed, Aug 08, 2018 at 01:17:49PM +0200, Bernhard Reutner-Fischer wrote: > On 7 August 2018 18:34:30 CEST, Segher Boessenkool > wrote: > >On Mon, Aug 06, 2018 at 08:25:49AM -0700, Mike Stump wrote: > >> Since g++ already requires 1.5.3, it make no sense to bump to > >anything older that 1.5.3,

Ping for STRING_CST patches

Hi, I'd like to ping the following patches: [PATCH] Check the STRING_CSTs in varasm.c https://gcc.gnu.org/ml/gcc-patches/2018-08/msg00361.html [PATCH] Fix not properly nul-terminated string constants in JIT https://gcc.gnu.org/ml/gcc-patches/2018-08/msg00370.html [PATCH] Handle overlength

Re: [PATCH][AArch64] Implement new intrinsics vabsd_s64 and vnegd_s64

On 01/08/18 18:35, James Greenhalgh wrote: On Wed, Aug 01, 2018 at 07:13:53AM -0500, Vlad Lazar wrote: On 31/07/18 22:48, James Greenhalgh wrote: On Fri, Jul 20, 2018 at 04:37:34AM -0500, Vlad Lazar wrote: Hi, The patch adds implementations for the NEON intrinsics vabsd_s64 and vnegd_s64.

[Bug tree-optimization/86724] Compilation error with new isl 0.20 (missing includes)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86724 Andrew Pinski changed: What|Removed |Added CC||freddie_chopin at op dot pl --- Comment

[Bug other/86890] GCC 8.2.0 fails to build with isl 0.20

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86890 Andrew Pinski changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|---

[Bug libstdc++/83982] [6 Regression] Exception guarantee of C++14 vector::resize(size_type) is not met

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83982 --- Comment #12 from Jonathan Wakely --- Author: redi Date: Wed Aug 8 16:31:55 2018 New Revision: 263427 URL: https://gcc.gnu.org/viewcvs?rev=263427=gcc=rev Log: PR libstdc++/83982 fix exception-safety guarantee of std::vector::resize

[Bug libstdc++/83982] [6 Regression] Exception guarantee of C++14 vector::resize(size_type) is not met

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83982 Jonathan Wakely changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|---

[Bug libstdc++/85768] [9 Regression] FreeBSD bootstrap fails due to undefined reference to 'backtrace'

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85768 Jonathan Wakely changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[PING] [PATCH] Create internally nul terminated string literals in fortan FE

Hi, I'd like to ping this patch: https://gcc.gnu.org/ml/fortran/2018-08/msg0.html I attach a new version, which contains only a minor white-space change from the previous version, in the function header of gfc_build_hollerith_string_const to contain "static tree" on one line instead of two.

[Bug tree-optimization/86886] Gcc miscompiles at -O3 on valid code

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86886 Qirun Zhang changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|---

Re: [PATCH] Make strlen range computations more conservative

On 08/08/18 17:51, Martin Sebor wrote: > On 08/07/2018 11:46 AM, Richard Biener wrote: >> >> Pointer types carry no information in GIMPLE. > > So what do you suggest as a solution? > > The strlen optimization can be decoupled from warnings and > disabled, and the aggressive loop optimization can

Re: [PATCH] libstdc++-v3: Have aligned_alloc() on Newlib

On 08/08/18 15:46 +0100, Jonathan Wakely wrote: On 08/08/18 15:33 +0100, Jonathan Wakely wrote: On 08/08/18 16:22 +0200, Ulrich Weigand wrote: Jonathan Wakely wrote: Aha, so newlib was using memalign previously: @@ -53,20 +54,24 @@ aligned_alloc (std::size_t al, std::size_t sz) #else extern

[Bug libstdc++/80893] std::vector creation dereferences null pointer

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80893 Jonathan Wakely changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[Bug libstdc++/68519] condition_variable::wait_for does not work properly with float duration

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68519 Jonathan Wakely changed: What|Removed |Added Target Milestone|7.4 |6.5 --- Comment #13 from Jonathan

[Bug target/86448] GCC 9 compiler generates slower code for spec 2006 milc on a power9 using -mcpu=power9 than using -mcpu=power8

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86448 --- Comment #6 from kelvin at gcc dot gnu.org --- I should also clarify regarding all of the above comments that the numbers I have been reporting are the spec ratios. I had misunderstood that these ratios were encoded such that smaller values

Re: [PATCH] Make strlen range computations more conservative

On 08/07/2018 11:46 AM, Richard Biener wrote: On August 7, 2018 6:31:36 PM GMT+02:00, Martin Sebor wrote: On 08/07/2018 09:33 AM, Bernd Edlinger wrote: On 08/07/18 17:02, Martin Sebor wrote: On 08/06/2018 11:45 PM, Richard Biener wrote: On August 7, 2018 5:38:59 AM GMT+02:00, Martin Sebor

[Bug c++/67491] [meta-bug] concepts issues

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67491 Bug 67491 depends on bug 86493, which changed state. Bug 86493 Summary: [concepts] Hard error for "call to non-'constexpr' function" in a requires expression https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86493 What|Removed

[Bug c++/86493] [concepts] Hard error for "call to non-'constexpr' function" in a requires expression

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86493 Casey Carter changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|---

[Bug libstdc++/86292] Missing exception safety when constructing vector from input iterator pair

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86292 Jonathan Wakely changed: What|Removed |Added Target Milestone|7.4 |6.5 --- Comment #9 from Jonathan

[Bug libstdc++/60555] std::system_category().default_error_condition() doesn't map system errno values to std::generic_category()

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=60555 Jonathan Wakely changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|---

[Bug libstdc++/86597] directory_entry::exist et al forget to clear the error_code.

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86597 Jonathan Wakely changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|---

[Bug libstdc++/80893] std::vector creation dereferences null pointer

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80893 --- Comment #7 from Jonathan Wakely --- Author: redi Date: Wed Aug 8 15:40:47 2018 New Revision: 263421 URL: https://gcc.gnu.org/viewcvs?rev=263421=gcc=rev Log: PR libstdc++/80893 Fix null dereference in vector Backport from mainline

[Bug libstdc++/68519] condition_variable::wait_for does not work properly with float duration

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68519 --- Comment #12 from Jonathan Wakely --- Author: redi Date: Wed Aug 8 15:40:41 2018 New Revision: 263420 URL: https://gcc.gnu.org/viewcvs?rev=263420=gcc=rev Log: PR libstdc++/68519 use native duration to avoid rounding errors Backport from

[Bug libstdc++/60555] std::system_category().default_error_condition() doesn't map system errno values to std::generic_category()

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=60555 --- Comment #15 from Jonathan Wakely --- Author: redi Date: Wed Aug 8 15:40:26 2018 New Revision: 263417 URL: https://gcc.gnu.org/viewcvs?rev=263417=gcc=rev Log: PR libstdc++/60555 std::system_category() should recognise POSIX errno values

[Bug libstdc++/86734] [DR 2188] reverse_iterator::operator-> does not support overloaded operator

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86734 --- Comment #6 from Jonathan Wakely --- Author: redi Date: Wed Aug 8 15:40:21 2018 New Revision: 263416 URL: https://gcc.gnu.org/viewcvs?rev=263416=gcc=rev Log: PR libstdc++/86734 use addressof in reverse_iterator::operator-> Backport from

[Bug libstdc++/86292] Missing exception safety when constructing vector from input iterator pair

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86292 --- Comment #8 from Jonathan Wakely --- Author: redi Date: Wed Aug 8 15:40:37 2018 New Revision: 263419 URL: https://gcc.gnu.org/viewcvs?rev=263419=gcc=rev Log: PR libstdc++/86292 fix exception safety of std::vector constructor Backport from

[Bug rtl-optimization/86882] [9 Regression] ICE in reg_overlap_mentioned_p, at rtlanal.c:1873

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86882 --- Comment #4 from Uroš Bizjak --- (In reply to Segher Boessenkool from comment #3) > combine creates a clobber of const_int 0 to make sure a pattern will > not match. That is valid RTL, but further patterns constructed from > that are not

[Bug libstdc++/66145] [5/6/7 Regression] std::ios_base::failure objects thrown from libstdc++.so use old ABI

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66145 --- Comment #37 from Jonathan Wakely --- Author: redi Date: Wed Aug 8 15:40:11 2018 New Revision: 263414 URL: https://gcc.gnu.org/viewcvs?rev=263414=gcc=rev Log: PR libstdc++/66145 allow catching iostream errors as cxx11 ios::failure Define a

[Bug libstdc++/85222] [7 Regression] ABI breakage of __throw_ios_failure by r244498

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85222 --- Comment #24 from Jonathan Wakely --- Author: redi Date: Wed Aug 8 15:40:11 2018 New Revision: 263414 URL: https://gcc.gnu.org/viewcvs?rev=263414=gcc=rev Log: PR libstdc++/66145 allow catching iostream errors as cxx11 ios::failure Define a

Re: [PATCH] line-map include-from representation

On Wed, 2018-08-08 at 11:36 -0400, David Malcolm wrote: > On Wed, 2018-08-08 at 11:28 -0400, Nathan Sidwell wrote: > > On 08/08/2018 10:46 AM, David Malcolm wrote: > > > > > [...snip...] > > > > > > We don't seem to have much test coverage for this code. Sorry to > > > be a > > > pain, but

Re: [PATCH] line-map include-from representation

On Wed, 2018-08-08 at 11:28 -0400, Nathan Sidwell wrote: > On 08/08/2018 10:46 AM, David Malcolm wrote: > > > [...snip...] > > > > We don't seem to have much test coverage for this code. Sorry to > > be a > > pain, but could you please try adding a testcase of a diagnostic > > issued > > from

[Bug libstdc++/86597] directory_entry::exist et al forget to clear the error_code.

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86597 --- Comment #2 from Jonathan Wakely --- Author: redi Date: Wed Aug 8 15:33:32 2018 New Revision: 263412 URL: https://gcc.gnu.org/viewcvs?rev=263412=gcc=rev Log: PR libstdc++/86597 directory_entry observers should clear error_code PR

[Bug c++/86767] [6/7 Regression] continue statements in constexpr functions causes unbounded looping

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86767 Marek Polacek changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|---

[Bug c++/86767] [6/7/8 Regression] continue statements in constexpr functions causes unbounded looping

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86767 --- Comment #6 from Marek Polacek --- Author: mpolacek Date: Wed Aug 8 15:30:50 2018 New Revision: 263410 URL: https://gcc.gnu.org/viewcvs?rev=263410=gcc=rev Log: PR c++/86767 * constexpr.c (cxx_eval_statement_list): Handle

[Bug target/84332] ICE in insn_default_length, at config/s390/s390.md:9697 for -fstack-clash-protection

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84332 Andreas Krebbel changed: What|Removed |Added Status|UNCONFIRMED |ASSIGNED Last reconfirmed|

Re: [PATCH] line-map include-from representation

On 08/08/2018 10:46 AM, David Malcolm wrote: [...snip...] We don't seem to have much test coverage for this code. Sorry to be a pain, but could you please try adding a testcase of a diagnostic issued from within a couple of levels of nested includes, perhaps using /* { dg-options

[Bug target/79895] ICE in extract_constrain_insn, at recog.c:2213

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79895 Andreas Krebbel changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|---

[Bug other/86890] GCC 8.2.0 fails to build with isl 0.20

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86890 --- Comment #2 from Freddie Chopin --- Prerequisites docs say "isl Library version 0.15 or later". Configure script also accepts 0.20 just fine. BTW - 0.19 builds and works OK.

[Bug target/85295] ICE in extract_constrain_insn, at recog.c:2205

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85295 Andreas Krebbel changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|---

[Bug c++/86082] user-defined literals are not converted to the execution charset

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86082 Andreas Krebbel changed: What|Removed |Added Status|RESOLVED|CLOSED --- Comment #9 from Andreas

[Bug c++/86082] user-defined literals are not converted to the execution charset

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86082 Andreas Krebbel changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

Re: [PATCH,nvptx] Use CUDA driver API to select default runtime launch, geometry

On Wed, Aug 08, 2018 at 07:09:16AM -0700, Cesar Philippidis wrote: > On 08/07/2018 06:52 AM, Cesar Philippidis wrote: > > > I attached an updated version of the CUDA driver patch, although I > > haven't rebased it against your changes yet. It still needs to be tested > > against CUDA 5.5 using

[Bug other/86890] GCC 8.2.0 fails to build with isl 0.20

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86890 --- Comment #1 from graham.stott77 at gmail dot com --- isl  0.18 is the supported version for gcc 8 branch. Original message From: freddie_chopin at op dot pl Date: 08/08/2018 16:04 (GMT+00:00) To: gcc-bugs@gcc.gnu.org

Re: [Bug other/86890] New: GCC 8.2.0 fails to build with isl 0.20

isl  0.18 is the supported version for gcc 8 branch. Original message From: freddie_chopin at op dot pl Date: 08/08/2018 16:04 (GMT+00:00) To: gcc-bugs@gcc.gnu.org Subject: [Bug other/86890] New: GCC 8.2.0 fails to build with isl 0.20

[Bug rtl-optimization/83420] S/390 bootstrap failure starting with r255569

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83420 Andreas Krebbel changed: What|Removed |Added Status|RESOLVED|CLOSED --- Comment #4 from Andreas

[Bug rtl-optimization/83420] S/390 bootstrap failure starting with r255569

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83420 Andreas Krebbel changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|---

[Bug other/86890] New: GCC 8.2.0 fails to build with isl 0.20

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86890 Bug ID: 86890 Summary: GCC 8.2.0 fails to build with isl 0.20 Product: gcc Version: 8.2.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: other

[Bug target/86448] GCC 9 compiler generates slower code for spec 2006 milc on a power9 using -mcpu=power9 than using -mcpu=power8

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86448 --- Comment #5 from kelvin at gcc dot gnu.org --- I apologize for an error in the previous comment. The two columns should have been labeled -mcpu=power8 (left) and -mcpu=power9 (right) instead of gcc8 and gcc9.

Re: [PATCH] libstdc++-v3: Have aligned_alloc() on Newlib

On 08/08/18 15:33 +0100, Jonathan Wakely wrote: On 08/08/18 16:22 +0200, Ulrich Weigand wrote: Jonathan Wakely wrote: Aha, so newlib was using memalign previously: @@ -53,20 +54,24 @@ aligned_alloc (std::size_t al, std::size_t sz) #else extern "C" void *memalign(std::size_t boundary,

Re: [PATCH] line-map include-from representation

On Wed, 2018-08-08 at 09:06 -0400, Nathan Sidwell wrote: > This patch changes the way line-maps hold the included-from > information. > Currently this is an index to another (earlier) line-map, and > relies > on the fact that #include cause the termination of the current map > and > emission

Re: dejagnu version update?

Hi, On Wed, 8 Aug 2018, Bernhard Reutner-Fischer wrote: > How come? > > If one wants to develop on a distro that is notoriously outdated then > you have to obtain the missing pieces yourself. It's not about developing on an "notoriously outdated" distro, but about _testing_ on it. There are

Re: dejagnu version update?

Hi, On Wed, 8 Aug 2018, Bernhard Reutner-Fischer wrote: > How come? > > If one wants to develop on a distro that is notoriously outdated then > you have to obtain the missing pieces yourself. It's not about developing on an "notoriously outdated" distro, but about _testing_ on it. There are

[committed][libgomp, nvptx] Fall back to cuLinkAddData/cuLinkCreate if _v2 not found

On Tue, Aug 07, 2018 at 06:52:59AM -0700, Cesar Philippidis wrote: > I spotted an error > with the patch; I realized that the cuda.h that ships with libgomp > emulates version CUDA 8.0. That lead to problems using cuLinkAddData, > because that function gets remapped to cuLinkAddData_v2 in CUDA

Re: [PATCH] libstdc++-v3: Have aligned_alloc() on Newlib

On 08/08/18 16:22 +0200, Ulrich Weigand wrote: Jonathan Wakely wrote: Aha, so newlib was using memalign previously: @@ -53,20 +54,24 @@ aligned_alloc (std::size_t al, std::size_t sz) #else extern "C" void *memalign(std::size_t boundary, std::size_t size); #endif -#define aligned_alloc

[committed][libgomp, nvptx] Allow cuGetErrorString to be NULL

Hi, Cuda driver api function cuGetErrorString is available in version 6.0 and higher. Currently, when the driver that is used does not contain this function, the libgomp nvptx plugin will not build (PLUGIN_NVPTX_DYNAMIC == 0) or run (PLUGIN_NVPTX_DYNAMIC == 1). This patch fixes this problem by

[committed][libgomp, nvptx] Remove hard-coded const in nvptx_open_device

Hi, CU_DEVICE_ATTRIBUTE_MAX_REGISTERS_PER_MULTIPROCESSOR is defined in cuda driver api version 6.0 and higher. Currently nvptx_open_device uses a hard-coded constant instead. This patch fixes that by: - defining CU_DEVICE_ATTRIBUTE_MAX_REGISTERS_PER_MULTIPROCESSOR to the hardcoded constant at

[committed][libgomp, nvptx] Note that cuGetErrorString is in CUDA_VERSION >= 6000

Hi, Cuda driver api function cuGetErrorString is available in version 6.0 and higher. This patch: - removes a comment saying the declaration is not available in cuda.h 6.0 - fixes the presence test to use CUDA_VERSION < 6000 - moves the declaration to toplevel Build on x86_64 with nvptx

Re: [PATCH v3] Add HXT Phecda core support

On Wed, Aug 08, 2018 at 05:38:09AM -0500, Hongbo Zhang wrote: > HXT semiconductor's CPU core Phecda, as a variant of Qualcomm qdf24xx, > reuses the same tuning structure and pipeline with it. Thank you. This patch is still OK. I've applied it on your behalf as r263404. Thanks, James > >

Re: [PATCH] libstdc++-v3: Have aligned_alloc() on Newlib

Jonathan Wakely wrote: > Aha, so newlib was using memalign previously: > > @@ -53,20 +54,24 @@ aligned_alloc (std::size_t al, std::size_t sz) > #else > extern "C" void *memalign(std::size_t boundary, std::size_t size); > #endif > -#define aligned_alloc memalign Yes, exactly ... this commit

Re: [PATCH] libstdc++-v3: Have aligned_alloc() on Newlib

On 08/08/18 16:04 +0200, Sebastian Huber wrote: On 08/08/18 16:01, Jonathan Wakely wrote: On 08/08/18 15:57 +0200, Ulrich Weigand wrote: Jonathan Wakely wrote: On 08/08/18 10:52 +0200, Sebastian Huber wrote: While building for Newlib, some configure checks must be hard coded. The

Re: [PATCH,nvptx] Use CUDA driver API to select default runtime launch, geometry

On 08/07/2018 06:52 AM, Cesar Philippidis wrote: > I attached an updated version of the CUDA driver patch, although I > haven't rebased it against your changes yet. It still needs to be tested > against CUDA 5.5 using the systems/Nvidia's cuda.h. But I wanted to give > you an update. > > Does

  1   2   >