Re: Clobber REG_CC only for some constraint alternatives?

Hans-Peter Nilsson writes: > On Wed, 19 Aug 2020, Senthil Kumar Selvaraj wrote: >> >> Hans-Peter Nilsson writes: >> >> > On Fri, 14 Aug 2020, Senthil Kumar Selvaraj via Gcc wrote: >> >> As you can deduce from the (set_attr "cc" ..), only constraint >> >> alternatives 0,2,3 and 6 clobber CC -

[PATCH] Check calls before loop unrolling

Hi, When unroll loops, if there are calls inside the loop, those calls may raise negative impacts for unrolling. This patch adds a param param_max_unrolled_calls, and checks if the number of calls inside the loop bigger than this param, loop is prevent from unrolling. This patch is checking the

[Bug c++/96720] New: ICE with* after include

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96720 Bug ID: 96720 Summary: ICE with* after include Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++

[PATCH PR96698] aarch64: ICE during GIMPLE pass:vect

Hi, This is a simple fix for PR96698. For the test case, there are two PHIs in the inner loop in pass_vect [local count: 719407024]: # b_26 = PHI <0(4), b_15(10)> # c_27 = PHI <0(4), b_26(10)> c_27 = PHI <0(4), b_26(10)>

Re: [Patch 3/5] rs6000, Add TI to TD (128-bit DFP) and TD to TI support

Hi! On Tue, Aug 11, 2020 at 12:22:59PM -0700, Carl Love wrote: > +(define_insn "floattitd2" > + [(set (match_operand:TD 0 "gpc_reg_operand" "=d") > + (float:TD (match_operand:TI 1 "gpc_reg_operand" "v")))] > + "TARGET_TI_VECTOR_OPS" > + "dcffixqq %0,%1" > + [(set_attr "type" "dfp")]) I

[Bug analyzer/96713] [11 Regression] ICE: in fold_relational_const, at fold-const.c:14921 with -fanalyzer

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96713 David Malcolm changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|---

[committed] analyzer: fix ICE on vector comparisons [PR96713]

Successfully bootstrapped & regrtested on x86_64-pc-linux-gnu. Pushed to master as r11-2776-g2f5951bd95e334d611f4be7bbe1a136c580f9c20. gcc/analyzer/ChangeLog: PR analyzer/96713 * region-model.cc (region_model::get_gassign_result): For comparisons, only use eval_condition

[Bug analyzer/96713] [11 Regression] ICE: in fold_relational_const, at fold-const.c:14921 with -fanalyzer

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96713 --- Comment #2 from CVS Commits --- The master branch has been updated by David Malcolm : https://gcc.gnu.org/g:2f5951bd95e334d611f4be7bbe1a136c580f9c20 commit r11-2776-g2f5951bd95e334d611f4be7bbe1a136c580f9c20 Author: David Malcolm Date:

[Bug c++/96719] New: non-standard handling of alias templates used as template template arguments

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96719 Bug ID: 96719 Summary: non-standard handling of alias templates used as template template arguments Product: gcc Version: 11.0 Status: UNCONFIRMED Severity:

Re: [Patch 2/5] rs6000, 128-bit multiply, divide, modulo, shift, compare

On Thu, Aug 13, 2020 at 06:46:05PM -0500, will schmidt wrote: > > .../gcc.target/powerpc/int_128bit-runnable.c | 2254 + > > The path into the testsuite subdir looks strange there. Git abbreviated this. It is autogenerated (git diffstat), so there is nothing much you can do

Re: [PATCH, rs6000] Add non-relative jump table support on Power Linux

Hi! Sorry this took so long to review. "I lost track of this patch", what can I say :-/ On Fri, Aug 14, 2020 at 03:31:05PM +0800, HAO CHEN GUI wrote: > This patch adds non-relative jump table support on Power Linux. It > implements ASM_OUTPUT_ADDR_VEC_ELT and adds four new expansions for >

Re: [PATCH 2/5] C front end support to detect out-of-bounds accesses to array parameters

On Wed, 19 Aug 2020, Martin Sebor via Gcc-patches wrote: > > I think you need a while loop there, not just an if, to account for the > > case of multiple consecutive cdk_attrs. At least the GNU attribute syntax > > > > direct-declarator: > > [...] > > ( gnu-attributes[opt] declarator

RE: [PATCH] rs6000, restrict bfloat convert intrinsic to Power 10. Fix BU_P10V macro definitions.

On Wed, 2020-08-19 at 15:16 -0500, Segher Boessenkool wrote: > On Wed, Aug 19, 2020 at 02:19:12PM -0500, Peter Bergner wrote: > > On 8/14/20 7:42 PM, Segher Boessenkool wrote: > > > I think your current code is fine; I hadn't considered Bill's > > > upcoming > > > rewrite. It is more important to

Re: PING [Patch][Middle-end]Add -fzero-call-used-regs=[skip|used-gpr|all-gpr|used|all]

> On Aug 19, 2020, at 5:57 PM, Segher Boessenkool > wrote: > > Hi! > > On Wed, Aug 19, 2020 at 03:05:36PM -0500, Qing Zhao wrote: >> So, cleaning the scratch registers that are used to pass parameters at >> return instructions should >> effectively mitigate ROP attack. > > But that is

Re: [PATCH] bb-reorder: Remove a misfiring micro-optimization (PR96475)

Hi! On Wed, Aug 19, 2020 at 07:18:02PM +0100, Richard Sandiford wrote: > > I have never seen the second case misfiring in practice, only the first > > one! > > Shucks, I guessed the wrong way round :-) > > I'd argue that the first check isn't a micro-optimisation though. > It's testing whether

[Bug testsuite/96718] [11 regression] 25_algorithms/pstl/feature_test-3.cc has excess error after r11-2743

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96718 seurer at gcc dot gnu.org changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED

Re: PING [Patch][Middle-end]Add -fzero-call-used-regs=[skip|used-gpr|all-gpr|used|all]

Hi! On Wed, Aug 19, 2020 at 03:05:36PM -0500, Qing Zhao wrote: > So, cleaning the scratch registers that are used to pass parameters at return > instructions should > effectively mitigate ROP attack. But that is *very* expensive, in general. Instead of doing just a return instruction (which

Re: [PATCH 2/5] C front end support to detect out-of-bounds accesses to array parameters

On 8/17/20 4:09 PM, Joseph Myers wrote: On Thu, 13 Aug 2020, Martin Sebor via Gcc-patches wrote: * Maybe cdk_pointer is followed by cdk_attrs before cdk_id. In this case the code won't return. I think I see the problem you're pointing out (I just don't see how to trigger it or test that it

Re: Clobber REG_CC only for some constraint alternatives?

On Wed, 19 Aug 2020, Senthil Kumar Selvaraj wrote: > > Hans-Peter Nilsson writes: > > > On Fri, 14 Aug 2020, Senthil Kumar Selvaraj via Gcc wrote: > >> As you can deduce from the (set_attr "cc" ..), only constraint > >> alternatives 0,2,3 and 6 clobber CC - others leave it unchanged. > > > > Yes,

[Bug testsuite/96718] New: [11 regression] 25_algorithms/pstl/feature_test-3.cc has excess error after r11-2743

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96718 Bug ID: 96718 Summary: [11 regression] 25_algorithms/pstl/feature_test-3.cc has excess error after r11-2743 Product: gcc Version: 11.0 Status: UNCONFIRMED

[Bug c++/96717] New: -flifetime-dse=2 breaks webkit-gtk-2.28.4

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96717 Bug ID: 96717 Summary: -flifetime-dse=2 breaks webkit-gtk-2.28.4 Product: gcc Version: 11.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++

[Bug fortran/96711] Internal Compiler Error on NINT() Function

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96711 --- Comment #9 from Steve Kargl --- On Wed, Aug 19, 2020 at 09:36:32PM +, anlauf at gcc dot gnu.org wrote: > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96711 > > --- Comment #8 from anlauf at gcc dot gnu.org --- > A very quick hack seems

Re: [PATCH 3/4] libstdc++: Add floating-point std::to_chars implementation

On Wed, 22 Jul 2020, Patrick Palka wrote: > On Mon, 20 Jul 2020, Patrick Palka wrote: > > > On Mon, 20 Jul 2020, Jonathan Wakely wrote: > > > > > On 20/07/20 08:53 -0400, Patrick Palka via Libstdc++ wrote: > > > > On Mon, 20 Jul 2020, Jonathan Wakely wrote: > > > > > > > > > On 19/07/20 23:37

[Bug fortran/96711] Internal Compiler Error on NINT() Function

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96711 --- Comment #8 from anlauf at gcc dot gnu.org --- A very quick hack seems to solve the issue for me. For some reason the final fold_convert seems to create a problem. Does anybody know why? It there a shorter solution? diff --git

[Bug analyzer/96713] [11 Regression] ICE: in fold_relational_const, at fold-const.c:14921 with -fanalyzer

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96713 David Malcolm changed: What|Removed |Added Status|UNCONFIRMED |ASSIGNED Ever confirmed|0

[pushed] c++: Check satisfaction before non-dep convs. [CWG2369]

It's very hard to use concepts to protect a template from hard errors due to unwanted instantiation if constraints aren't checked until after doing all substitution and checking of non-dependent conversions. It was pretty straightforward to insert the satisfaction check into the logic, but I

[Bug c++/96199] [10/11 Regression] internal compiler error: in tsubst_copy with CTAD for alias templates

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96199 Jason Merrill changed: What|Removed |Added Resolution|--- |FIXED Status|ASSIGNED

[Bug c++/96716] New: GCC reports "object is private" when it's accessed through proper accessor

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96716 Bug ID: 96716 Summary: GCC reports "object is private" when it's accessed through proper accessor Product: gcc Version: 10.2.1 Status: UNCONFIRMED Severity:

[Bug tree-optimization/96715] New: Failure to optimize copysign of variable by negated variable

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96715 Bug ID: 96715 Summary: Failure to optimize copysign of variable by negated variable Product: gcc Version: 11.0 Status: UNCONFIRMED Severity: normal

[Bug tree-optimization/96714] New: Failure to optimize sqrt*sqrt of same variable with ffast-math

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96714 Bug ID: 96714 Summary: Failure to optimize sqrt*sqrt of same variable with ffast-math Product: gcc Version: 11.0 Status: UNCONFIRMED Severity: normal

Re: [EXTERNAL] Re: [PATCH] rs6000, restrict bfloat convert intrinsic to Power 10. Fix BU_P10V macro definitions.

On Wed, Aug 19, 2020 at 02:19:12PM -0500, Peter Bergner wrote: > On 8/14/20 7:42 PM, Segher Boessenkool wrote: > > I think your current code is fine; I hadn't considered Bill's upcoming > > rewrite. It is more important to make that go smoother than to fix some > > aesthetics right now. > > > >

[Bug fortran/96711] Internal Compiler Error on NINT() Function

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96711 Toon Moene changed: What|Removed |Added CC||toon at moene dot org --- Comment #7 from

[Bug fortran/96712] internal compiler error: in build_round_expr, at fortran/trans-intrinsic.c:399

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96712 Toon Moene changed: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED

Re: PING [Patch][Middle-end]Add -fzero-call-used-regs=[skip|used-gpr|all-gpr|used|all]

Hi, Based on all the previous discussion and more extensive study on ROP and its mitigation techniques these days, I came up with the following High-level proposal as requested, please take a look and let me know what I should change in this high-level design: > On Aug 6, 2020, at 6:37 PM,

[Bug analyzer/96713] New: [11 Regression] ICE: in fold_relational_const, at fold-const.c:14921 with -fanalyzer

LTO compression algorithms: zlib zstd gcc version 11.0.0 20200819 (experimental) (GCC)

[committed] [OG10] Re: Re: [Patch] [OpenMP, Fortran] Add structure/derived-type element mapping

If I got my tracking right, the og10 commit 4677091db1aa9d2a52e4839812bd73f47cc5e421 "[OpenMP, Fortran] Add structure/derived-type element mapping" regresses: [-PASS:-]{+FAIL:+} gfortran.dg/goacc/pr70828.f90 -O scan-tree-dump-times gimple "omp target oacc_data

[Bug fortran/96711] Internal Compiler Error on NINT() Function

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96711 anlauf at gcc dot gnu.org changed: What|Removed |Added CC||anlauf at gcc dot gnu.org

[Bug libstdc++/96042] Reference type of std::ranges::iota is __int128 with -std=c++2a?!

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96042 --- Comment #7 from CVS Commits --- The master branch has been updated by Jonathan Wakely : https://gcc.gnu.org/g:e6e01618e83bcd9eb3a2b27df30ed87106a748b4 commit r11-2773-ge6e01618e83bcd9eb3a2b27df30ed87106a748b4 Author: Jonathan Wakely Date:

Re: [committed] libstdc++: Make __int128 meet integer-class requirements [PR 96042]

On 19/08/20 17:00 +0100, Jonathan Wakely wrote: Because __int128 can be used as the difference type for iota_view, we need to ensure that it meets the requirements of an integer-class type. The requirements in [iterator.concept.winc] p10 include numeric_limits being specialized and giving

Re: GCC / GFortran (9.3.0; Cygwin 64) Internal Compiler Error on NINT() Function

Thanks. An internal compiler error is always a problem with the compiler itself. I submitted this to our bug tracker (Bugzilla) as Problem Report 96712 on your behalf. Follow it by looking at https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96712 Kind regards, Toon. On 8/19/20 4:22 PM, Bernd

[Bug fortran/96712] New: internal compiler error: in build_round_expr, at fortran/trans-intrinsic.c:399

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96712 Bug ID: 96712 Summary: internal compiler error: in build_round_expr, at fortran/trans-intrinsic.c:399 Product: gcc Version: 10.2.0 Status: UNCONFIRMED

[Bug analyzer/96643] [11 Regression] ICE in deref_rvalue, at analyzer/region-model.cc:1288

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96643 David Malcolm changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|---

[Bug analyzer/96705] [11 Regression] ICE: in wide_int_to_tree_1, at tree.c:1612 with -fanalyzer

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96705 David Malcolm changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|---

[Bug analyzer/96699] [11 Regression] ICE in fold_convert_const_int_from_real, at fold-const.c:2038

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96699 David Malcolm changed: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED

[committed] analyzer: fix ICE converting float to int [PR96699]

Successfully bootstrapped & regrtested on x86_64-pc-linux-gnu. Pushed to master as r11-2770-g366bd1ac01a5249a463e64234674ad2d174faa9a. gcc/analyzer/ChangeLog: PR analyzer/96699 * region-model-manager.cc (region_model_manager::get_or_create_cast): Use FIX_TRUNC_EXPR for

[committed] analyzer: fix ICE on deref_rvalue on SK_COMPOUND [PR96643]

Successfully bootstrapped & regrtested on x86_64-pc-linux-gnu. Pushed to master as r11-2772-g23ebfda0e352fa0a92c6b012458ecb65505a135f. gcc/analyzer/ChangeLog: PR analyzer/96643 * region-model.cc (region_model::deref_rvalue): Rather than attempting to handle all svalue

[committed] analyzer: fix ICE on folding vector 0 [PR96705]

Successfully bootstrapped & regrtested on x86_64-pc-linux-gnu. Pushed to master as r11-2771-gfc02b568e2cd3f6a28d4b7c1063bbf8842c89aad. gcc/analyzer/ChangeLog: * region-model-manager.cc PR analyzer/96705 (region_model_manager::maybe_fold_binop): Check that we have an

[Bug analyzer/96643] [11 Regression] ICE in deref_rvalue, at analyzer/region-model.cc:1288

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96643 --- Comment #2 from CVS Commits --- The master branch has been updated by David Malcolm : https://gcc.gnu.org/g:23ebfda0e352fa0a92c6b012458ecb65505a135f commit r11-2772-g23ebfda0e352fa0a92c6b012458ecb65505a135f Author: David Malcolm Date:

[Bug analyzer/96705] [11 Regression] ICE: in wide_int_to_tree_1, at tree.c:1612 with -fanalyzer

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96705 --- Comment #2 from CVS Commits --- The master branch has been updated by David Malcolm : https://gcc.gnu.org/g:fc02b568e2cd3f6a28d4b7c1063bbf8842c89aad commit r11-2771-gfc02b568e2cd3f6a28d4b7c1063bbf8842c89aad Author: David Malcolm Date:

[Bug analyzer/96699] [11 Regression] ICE in fold_convert_const_int_from_real, at fold-const.c:2038

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96699 --- Comment #1 from CVS Commits --- The master branch has been updated by David Malcolm : https://gcc.gnu.org/g:366bd1ac01a5249a463e64234674ad2d174faa9a commit r11-2770-g366bd1ac01a5249a463e64234674ad2d174faa9a Author: David Malcolm Date:

Re: [EXTERNAL] Re: [PATCH] rs6000, restrict bfloat convert intrinsic to Power 10. Fix BU_P10V macro definitions.

On 8/14/20 7:42 PM, Segher Boessenkool wrote: > I think your current code is fine; I hadn't considered Bill's upcoming > rewrite. It is more important to make that go smoother than to fix some > aesthetics right now. > > Please check if the names for the builtins match the (future) >

[PATCH] rs6000: Fix extraneous characters in the documentation

Replace them with a whitespace in order to avoid artifacts in the HTML document. 2020-08-19 Tulio Magno Quites Machado Filho gcc/ * doc/extend.texi (PowerPC Built-in Functions): Replace extraneous characters with whitespace. --- gcc/doc/extend.texi | 6 +++--- 1 file changed,

Re: [PATCH] bb-reorder: Remove a misfiring micro-optimization (PR96475)

Segher Boessenkool writes: > On Wed, Aug 19, 2020 at 01:10:36PM +0100, Richard Sandiford wrote: >> Segher Boessenkool writes: >> > When the compgotos pass copies the tail of blocks ending in an indirect >> > jump, there is a micro-optimization to not copy the last one, since the >> > original

[Bug analyzer/94858] False report of memory leak

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94858 --- Comment #3 from David Malcolm --- It looks like we lose the: cluster for: (*INIT_VAL(td_14(D))) ESCAPED key: {kind: direct, start: 0, size: 64, next: 64} value: ‘hashNx *’ {_ALLOCATED_REGION(0)} at the

[Bug fortran/96711] Internal Compiler Error on NINT() Function

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96711 --- Comment #5 from kargl at gcc dot gnu.org --- Trivial workaround. program nint_error implicit none integer(kind=16) :: m real(8) :: x, y x = 1 y = x - 1 m = anint(y) print *, m end This will use

Re: [PATCH] rs6000: Enable more sibcalls when TOC is not preserved

Hi! On Wed, Aug 19, 2020 at 09:40:16AM -0500, Bill Schmidt wrote: > A function compiled with the PC-relative addressing model does not > require r2 to contain a TOC pointer, and does not guarantee that r2 > will be preserved for its caller. Such a function can make sibcalls > without restriction

[Bug analyzer/94858] False report of memory leak

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94858 David Malcolm changed: What|Removed |Added Last reconfirmed||2020-08-19

Re: [PATCH 1/2] Add new RTX instruction class FILLER_INSN

Segher Boessenkool writes: > [ Please don't post new patch series as replies to old ] > > On Wed, Jul 22, 2020 at 12:02:33PM +0200, Andrea Corallo wrote: >> This first patch implements the addition of a new RTX instruction class >> FILLER_INSN, which has been white listed to allow placement of

[Bug other/91085] fixincludes breaks

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91085 Tendel10 at protonmail dot com changed: What|Removed |Added CC||Tendel10 at protonmail

Re: [PATCH] bb-reorder: Remove a misfiring micro-optimization (PR96475)

On Wed, Aug 19, 2020 at 01:10:36PM +0100, Richard Sandiford wrote: > Segher Boessenkool writes: > > When the compgotos pass copies the tail of blocks ending in an indirect > > jump, there is a micro-optimization to not copy the last one, since the > > original block will then just be deleted.

[Bug fortran/96711] Internal Compiler Error on NINT() Function

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96711 kargl at gcc dot gnu.org changed: What|Removed |Added CC||kargl at gcc dot gnu.org

Re: [PATCH 1/2] Add new RTX instruction class FILLER_INSN

On Wed, Aug 19, 2020 at 11:13:40AM +0200, Andrea Corallo wrote: > Segher Boessenkool writes: > > So I wonder if this cannot be done with some kind of NOTE, instead? > > I was having a look into reworking this using an insn note as (IIUC) > suggested. The idea is appealing but looking into

Re: [PATCH 1/2] Add new RTX instruction class FILLER_INSN

[ Please don't post new patch series as replies to old ] On Wed, Jul 22, 2020 at 12:02:33PM +0200, Andrea Corallo wrote: > This first patch implements the addition of a new RTX instruction class > FILLER_INSN, which has been white listed to allow placement of NOPs > outside of a basic block.

Re: [PATCH] PR libstdc++/71579 assert that type traits are not misused with an incomplete type

ср, 19 авг. 2020 г. в 14:29, Jonathan Wakely : <...> > Do we also want to check > (std::__is_complete_or_unbounded(__type_identity<_ArgTypes>{}) && ...) > for invoke_result and the is_invocable traits? > > We can use a fold expression there, because those traits are not > defined before C++17.

[committed] libstdc++: Remove deprecated comparison operators for RB trees

These functions were deprecated in GCC 9.1.0 because they are never used by the library. This patch removes them for GCC 11. libstdc++-v3/ChangeLog: * include/bits/stl_tree.h (operator!=, operator>, operator<=) (operator>=): Remove deprecated functions. Tested powerpc64le-linux.

[PATCH v2][GCC] arm: Add +nomve and +nomve.fp options to -mcpu=cortex-m55

From: Joe Ramsay Hi all, This patch rearranges feature bits for MVE and FP to implement the following flags for -mcpu=cortex-m55. - +nomve:equivalent to armv8.1-m.main+fp.dp+dsp. - +nomve.fp: equivalent to armv8.1-m.main+mve+fp.dp (+dsp is implied by +mve). - +nofp: equivalent to

[committed] libstdc++: Make __int128 meet integer-class requirements [PR 96042]

Because __int128 can be used as the difference type for iota_view, we need to ensure that it meets the requirements of an integer-class type. The requirements in [iterator.concept.winc] p10 include numeric_limits being specialized and giving meaningful answers. Currently we only specialize

[Bug libstdc++/96042] Reference type of std::ranges::iota is __int128 with -std=c++2a?!

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96042 --- Comment #6 from CVS Commits --- The master branch has been updated by Jonathan Wakely : https://gcc.gnu.org/g:386fd16c551188e20d5b1684b7139e4269f9a739 commit r11-2766-g386fd16c551188e20d5b1684b7139e4269f9a739 Author: Jonathan Wakely Date:

[Bug libstdc++/96042] Reference type of std::ranges::iota is __int128 with -std=c++2a?!

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96042 Jonathan Wakely changed: What|Removed |Added Assignee|unassigned at gcc dot gnu.org |redi at gcc dot gnu.org

[Bug fortran/96711] Internal Compiler Error on NINT() Function

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96711 --- Comment #3 from B Eggen --- Here is the latest f90 file: program nint_error integer :: n, m integer(kind=16) :: i, j, nint integer, parameter :: idp=selected_real_kind(9,99) integer, parameter :: i16=selected_int_kind(38)

[Bug fortran/96711] Internal Compiler Error on NINT() Function

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96711 --- Comment #2 from B Eggen --- adding the compiler flag -fdefault-integer-8 extends the range somewhat, but I really require NINT() to work for whole range (up to 2^127-1): -> ./nint_error.e i16= 16 170141183460469231731687303715884105727 1 1

[Bug fortran/96711] Internal Compiler Error on NINT() Function

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96711 B Eggen changed: What|Removed |Added CC||bre08 at eggen dot co.uk --- Comment #1 from

[committed] i386: Use code_for_ instead of gen_ for parameterized names more.

Some builtins are better expanded to patterns with parametrized names via code_for_ than gen_ helpers. No functional changes. 2020-08-19 Uroš Bizjak gcc/ChangeLog: * config/i386/i386-expand.c (ix86_expand_builtin) [case IX86_BUILTIN_ENQCMD, case IX86_BUILTIN_ENQCMDS]: Rewrite

[Bug fortran/96711] New: Internal Compiler Error on NINT() Function

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96711 Bug ID: 96711 Summary: Internal Compiler Error on NINT() Function Product: gcc Version: 9.3.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component:

[Bug libstdc++/96710] New: __int128 vs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96710 Bug ID: 96710 Summary: __int128 vs Product: gcc Version: 11.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: libstdc++ Assignee:

[PING][PATCH] correct handling of indices into arrays with elements larger than 1 (PR c++/96511)

Ping: https://gcc.gnu.org/pipermail/gcc-patches/2020-August/551783.html On 8/11/20 10:19 AM, Martin Sebor wrote: -Wplacement-new handles array indices and pointer offsets the same: by adjusting them by the size of the element.  That's correct for the latter but wrong for the former, causing

[Bug c++/96709] New: cmov and vectorization

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96709 Bug ID: 96709 Summary: cmov and vectorization Product: gcc Version: unknown URL: https://godbolt.org/z/GKnj17 Status: UNCONFIRMED Severity: normal

[wwwdocs] Remove stray '>' character

Pushed to wwwdocs. commit e8120aa3ecc3dec9c6ddcd3add2326e94fe5fb1e Author: Jonathan Wakely Date: Wed Aug 19 15:41:44 2020 +0100 Remove stray '>' character diff --git a/htdocs/bugs/index.html b/htdocs/bugs/index.html index 66d9138f..a6631d8a 100644 --- a/htdocs/bugs/index.html +++

Re: [PATCH] rs6000: Enable more sibcalls when TOC is not preserved

I failed to mention that this has been bootstrapped and tested on powerpc64le-unknown-linux-gnu, with no regressions.  Is this ok for trunk? Thanks, Bill On 8/19/20 9:40 AM, Bill Schmidt via Gcc-patches wrote: A function compiled with the PC-relative addressing model does not require r2 to

[PATCH] rs6000: Enable more sibcalls when TOC is not preserved

A function compiled with the PC-relative addressing model does not require r2 to contain a TOC pointer, and does not guarantee that r2 will be preserved for its caller. Such a function can make sibcalls without restriction based on TOC preservation rules. However, a caller that does preserve r2

Re: GCC / GFortran (9.3.0; Cygwin 64 and Ubuntu) Internal Compiler Error on NINT() Function

On Wed, Aug 19, 2020 at 10:34 AM Bernd Eggen via Gcc wrote: > > Hello, > > I realised when I created the small code snippet I accidentally put the > variable "m" in the default integer declaration, I checked it and moving it > (to kind=16) does not make a difference either. > > I also checked on

Re: GCC / GFortran (9.3.0; Cygwin 64 and Ubuntu) Internal Compiler Error on NINT() Function

Hello, I realised when I created the small code snippet I accidentally put the variable "m" in the default integer declaration, I checked it and moving it (to kind=16) does not make a difference either. I also checked on Ubuntu-64, same GCC & GFortran version (9.3.0) and I get the same error

[Bug tree-optimization/94234] missed ccp folding for (addr + 8 * n) - (addr + 8 * (n - 1))

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94234 --- Comment #3 from CVS Commits --- The master branch has been updated by Feng Xue : https://gcc.gnu.org/g:459f6f68a75fe88e7c8309ca8ad3244a532b0d8e commit r11-2764-g459f6f68a75fe88e7c8309ca8ad3244a532b0d8e Author: Feng Xue Date: Mon Jun 1

Re: GCC / GFortran (9.3.0; Cygwin 64) Internal Compiler Error on NINT() Function

On Wed, 19 Aug 2020 at 15:24, Bernd Eggen via Gcc wrote: > > Hello, > > I've come across an internal compiler error (in GFortran), concerning the > function NINT(), Then you should be reporting it to Bugzilla, not to this mailing list. > Please submit a full bug report, > with preprocessed

[Bug c++/61372] Add warning to detect noexcept functions that might throw

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61372 --- Comment #6 from Jonathan Wakely --- (In reply to David Crocker from comment #5) > You seem to be assuming that C++ exceptions can propagate through functions > compiled with a C compiler. I'm not assuming anything. I know for a fact that

GCC / GFortran (9.3.0; Cygwin 64) Internal Compiler Error on NINT() Function

Hello, I've come across an internal compiler error (in GFortran), concerning the function NINT(), I attach a very simple source code that illustrates the error. Essentially I am working with 16-byte integers, and there seems no way to ensure that NINT() returns the correct precision integer. [I

[Bug c++/61372] Add warning to detect noexcept functions that might throw

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61372 --- Comment #5 from David Crocker --- You seem to be assuming that C++ exceptions can propagate through functions compiled with a C compiler. On most platforms, they normally cannot, because a C compiler does not produce the information needed

[Bug target/96706] [nvptx] compilation failure of pr89663-1.c

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96706 Tom de Vries changed: What|Removed |Added Target||nvptx --- Comment #1 from Tom de Vries

Re: [committed] libstdc++: Add deprecated attributes to old iostream members

On 19/08/20 12:29 +0100, Jonathan Wakely wrote: Back in 2017 I removed these prehistoric members (which were deprecated since C++98) for C++17 mode. But I didn't add deprecated attributes to most of them, so users didn't get any warning they would be going away. Apparently some poor souls do

[Bug analyzer/96705] [11 Regression] ICE: in wide_int_to_tree_1, at tree.c:1612 with -fanalyzer

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96705 David Malcolm changed: What|Removed |Added Ever confirmed|0 |1 Last reconfirmed|

Re: [PATCH v2] libgcc: Use `-fasynchronous-unwind-tables' for LIB2_DIVMOD_FUNCS

On 19/08/2020 13:54, Maciej W. Rozycki via Gcc-patches wrote: > On Tue, 18 Aug 2020, Richard Earnshaw wrote: > >>> Complement commit b932f770f70d ("x86_64 frame unwind info"), SVN r46374, >>> , and replace >>> `-fexceptions

[Bug tree-optimization/96708] Failure to optimize max pattern with comparison when using a temporary variable

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96708 --- Comment #1 from Gabriel Ravier --- PS: This especially affects, for example, C++ code that uses std::max, which fails to optimize properly compared to, for example, a `max` macro.

[Bug tree-optimization/96708] New: Failure to optimize max pattern with comparison when using a temporary variable

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96708 Bug ID: 96708 Summary: Failure to optimize max pattern with comparison when using a temporary variable Product: gcc Version: 11.0 Status: UNCONFIRMED Severity:

PING [PATCH] x86: Inline strncmp only with -minline-all-stringops

On Wed, Jul 15, 2020 at 10:42:27AM -0700, H.J. Lu wrote: > Expand strncmp to "repz cmpsb" only with -minline-all-stringops since > "repz cmpsb" can be much slower than strncmp function implemented with > vector instructions, see > > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=43052 > > gcc/ >

[Bug target/95458] Inline strncmp is *much* slower than glibc

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95458 H.J. Lu changed: What|Removed |Added Ever confirmed|0 |1 Target Milestone|---

PING [PATCH] x86: Add cmpmemsi for -minline-all-stringops

On Tue, May 19, 2020 at 5:14 AM H.J. Lu wrote: > > On Tue, May 19, 2020 at 1:48 AM Uros Bizjak wrote: > > > > On Sun, May 17, 2020 at 7:06 PM H.J. Lu wrote: > > > > > > Duplicate the cmpstrn pattern for cmpmem. The only difference is that > > > the length argument of cmpmem is guaranteed to be

[Bug tree-optimization/96707] Failure to optimize right shift+unsigned compare of two variables optimally

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96707 --- Comment #1 from Gabriel Ravier --- PS: This transformation can also be done with a very similar pattern where the return statement is replaced with this : `return (x / y) <= x;`

[Bug tree-optimization/96707] New: Failure to optimize right shift+unsigned compare of two variables optimally

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96707 Bug ID: 96707 Summary: Failure to optimize right shift+unsigned compare of two variables optimally Product: gcc Version: 11.0 Status: UNCONFIRMED Severity:

[Bug target/96706] New: [nvptx] compilation failure of pr89663-1.c

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96706 Bug ID: 96706 Summary: [nvptx] compilation failure of pr89663-1.c Product: gcc Version: 11.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: target

Re: [PATCH v2] libgcc: Use `-fasynchronous-unwind-tables' for LIB2_DIVMOD_FUNCS

On Tue, 18 Aug 2020, Richard Earnshaw wrote: > > Complement commit b932f770f70d ("x86_64 frame unwind info"), SVN r46374, > > , and replace > > `-fexceptions -fnon-call-exceptions' with `-fasynchronous-unwind-tables' > > in

  1   2   >