Re: gcc/DATESTAMP wasn't updated since 20240507

On Thu, 9 May 2024, Jakub Jelinek wrote: > On Thu, May 09, 2024 at 12:14:43PM +0200, Jakub Jelinek wrote: > > On Thu, May 09, 2024 at 12:04:38PM +0200, Rainer Orth wrote: > > > I just noticed that gcc/DATESTAMP wasn't updated yesterday and today, > > > staying at 20240507. > > > > I think it is b

[committed] RISC-V: Fix typos in code or comment [NFC]

Just found some typo when fixing bugs and then use aspell to find few more typos, this patch didn't do anything other than fix typo. gcc/ChangeLog: * config/riscv/riscv-vsetvl.cc: Fix typos in comments. (get_all_predecessors): Ditto. (pre_vsetvl::m_unknow_info): Rename to.

Re: Ping: [PATCH v3] doc: Correction of Tree SSA Passes info.

On Thu, 9 May 2024, Chenghui Pan wrote: > Ping. Is this version of patch ok for trunk? thanks! Yes. I thought I approved the previous version conditional on the change. Richard. > On 2024/3/26 09:54, Chenghui Pan wrote: > > Current document of Tree SSA passes contains many parts that is not >

Re: [PATCH 1/4] rs6000: Make all 128 bit scalar FP modes have 128 bit precision [PR112993]

On Thu, May 9, 2024 at 9:12 PM Joseph Myers wrote: > > On Wed, 8 May 2024, Kewen.Lin wrote: > > > to widen IFmode to TFmode. To make build_common_tree_nodes > > be able to find the correct mode for long double type node, > > it introduces one hook mode_for_longdouble to offer target > > a way to

test mail

[PATCH-1v2] fwprop: Replace rtx_cost with insn_cost in try_fwprop_subst_pattern [PR113325]

Hi, This patch replaces rtx_cost with insn_cost in forward propagation. In the PR, one constant vector should be propagated and replace a pseudo in a store insn if we know it's a duplicated constant vector. It reduces the insn cost but not rtx cost. In this case, the cost is determined by destina

Re: [PATCH 1/2] RISC-V: Add tests for cpymemsi expansion

Hi Christoph, cpymemsi-1.c fails on a subset of newlib targets. "UNRESOLVED: gcc.target/riscv/cpymemsi-1.c   -O0  compilation failed to produce executable" Full list of failing targets here (New Failures section): https://github.com/patrick-rivos/gcc-postcommit-ci/issues/906 Thanks, Patri

[RISC-V] Use shNadd for constant synthesis

So here's the next idiom to improve constant synthesis. The basic idea here is to try and use shNadd to generate the constant when profitable. Let's take 0x30801. Right now that generates: li a0,3145728 addia0,a0,1 sllia0,a0,12 addia0,a0,-

Pushed: [PATCH] driver: Move -fdiagnostics-urls= early like -fdiagnostics-color= [PR114980]

On Thu, 2024-05-09 at 20:21 +, Joseph Myers wrote: > On Wed, 8 May 2024, Xi Ruoyao wrote: > > > In GCC 14 we started to emit URLs for "command-line option is > > valid for but not " and "-Werror= argument > > '-Werror=' is not valid for " warnings.  So we should > > have moved -fdiagnostics-

Re: [COMMITTED] Remove obsolete Solaris 11.3 support

The problem with illumos on SPARC is; illumos is also removing SPARC support piece by piece, especially as it gets in the way of what they want to do with the OS on x86-64 machines (which is what everyone in that community doing the main development uses). This was due to the lack of having a bu

Re: [x86 PATCH] Improve V[48]QI shifts on AVX512

On Fri, May 10, 2024 at 6:26 AM Roger Sayle wrote: > > > The following one line patch improves the code generated for V8QI and V4QI > shifts when AV512BW and AVX512VL functionality is available. + /* With AVX512 its cheaper to do vpmovsxbw/op/vpmovwb. */ + && !(TARGET_AVX512BW && TARGET

RE: [committed] testsuite: Fix up pr84508* tests [PR84508]

> -Original Message- > From: Jakub Jelinek > Sent: Friday, May 10, 2024 3:04 AM > To: Hongtao Liu > Cc: Hu, Lin1 ; gcc-patches@gcc.gnu.org; Liu, Hongtao > ; ubiz...@gmail.com > Subject: [committed] testsuite: Fix up pr84508* tests [PR84508] > > On Thu, May 09, 2024 at 12:45:42PM +0800, H

Re: [committed] Fix MIPS bootstrap

On Sun, 14 Jan 2024, Jeff Law wrote: > The condition for the pattern looks like this: > > "ISA_HAS_MIPS16E2" > > And if you dig into ISA_HAS_MIPS16E2: > > /* The MIPS16e V2 instructions are available. */ > #define ISA_HAS_MIPS16E2 (TARGET_MIPS16 && TARGET_MIPS16E2 \ >

New Croatian PO file for 'gcc' (version 14.1.0)

Hello, gentle maintainer. This is a message from the Translation Project robot. A revised PO file for textual domain 'gcc' has been submitted by the Croatian team of translators. The file is available at: https://translationproject.org/latest/gcc/hr.po (This file, 'gcc-14.1.0.hr.po', has j

[COMMITTED] Revert: "Enable prange support." [PR114985]

This reverts commit 36e877996936abd8bd08f8b1d983c8d1023a5842 until the IPA pass is fixed with regards to POINTER = POINTER POINTER. --- gcc/gimple-range-cache.cc | 4 ++-- gcc/gimple-range-fold.cc | 4 ++-- gcc/gimple-range-fold.h | 2 +- gcc/gimple-range-infer.cc | 2 +-

[x86 PATCH] Improve V[48]QI shifts on AVX512

The following one line patch improves the code generated for V8QI and V4QI shifts when AV512BW and AVX512VL functionality is available. For the testcase (from gcc.target/i386/vect-shiftv8qi.c): typedef signed char v8qi __attribute__ ((__vector_size__ (8))); v8qi foo (v8qi x) { return x >> 5; }

Re: [PATCH 1/4] RISC-V: Add test cases for cpymem expansion

On 5/7/24 11:17 PM, Christoph Müllner wrote: We have two mechanisms in the RISC-V backend that expand cpymem pattern: a) by-pieces, b) riscv_expand_block_move() in riscv-string.cc. The by-pieces framework has higher priority and emits a sequence of up to 15 instructions (see use_by_pieces_infr

Re: [patch,avr] PR114981: Implement __builtin_powif in assembly

On 5/8/24 4:10 AM, Georg-Johann Lay wrote: __builtin_powif is currently implemented in C, and this patch implements it (__powisf2) in assembly. Ok for master? Johann -- AVR: target/114981 - Tweak __powisf2 Implement __powisf2 in assembly. PR target/114981 libgcc/ * config/avr/t

Re: [PATCH] PR middle-end/111701: signbit(x*x) vs -fsignaling-nans

On Wed, 8 May 2024, Richard Biener wrote: > So it's reasonable to require -fnon-call-exceptions (which now enables > -fexceptions) and -fno-delete-dead-exceptions to have GCC preserve > a change of control flow side-effect of x*x? We do not preserve > FP exception bits set by otherwise unused ope

Re: [PATCH] Fortran: improve attribute conflict checking [PR93635]

Hi Mikael, Am 09.05.24 um 21:51 schrieb Mikael Morin: Hello, Le 06/05/2024 à 21:33, Harald Anlauf a écrit : Dear all, I've been contemplating whether to submit the attached patch. It addresses an ICE-on-invalid as reported in the PR, and also fixes an accepts-invalid (see testcase), plus mayb

Re: [PATCH] c++: lvalueness of non-dependent assignment [PR114994]

On Thu, 9 May 2024, Patrick Palka wrote: > Bootstrapped and regtested on x86_64-pc-linux-gnu, does this look > OK for trunk/14? For trunk as a follow-up I can implement the > mentionted representation change to use CALL_EXPR instead of > MODOP_EXPR for a non-dependent simple assignment expression

[PATCH] c++: lvalueness of non-dependent assignment [PR114994]

Bootstrapped and regtested on x86_64-pc-linux-gnu, does this look OK for trunk/14? For trunk as a follow-up I can implement the mentionted representation change to use CALL_EXPR instead of MODOP_EXPR for a non-dependent simple assignment expression that resolved to an operator= overload. -- >8 --

Re: [PATCH] driver: Move -fdiagnostics-urls= early like -fdiagnostics-color= [PR114980]

On Wed, 8 May 2024, Xi Ruoyao wrote: > In GCC 14 we started to emit URLs for "command-line option is > valid for but not " and "-Werror= argument > '-Werror=' is not valid for " warnings. So we should > have moved -fdiagnostics-urls= early like -fdiagnostics-color=, or > -fdiagnostics-urls= wou

Re: [PATCH] c++, mingw, v2: Fix up types of dtor hooks to __cxa_{,thread_}atexit/__cxa_throw on mingw ia32 [PR114968]

On 5/9/24 14:46, Jakub Jelinek wrote: On Thu, May 09, 2024 at 01:05:59PM -0400, Jason Merrill wrote: I think I'd rather pass ob_parm to start_cleanup_fn, where it can also replace the flag_use_cxa_atexit check in that function. Good idea, changed in the following patch. @@ -9998,7 +10004,8 @

Re: [PATCH] Fortran: improve attribute conflict checking [PR93635]

Hello, Le 06/05/2024 à 21:33, Harald Anlauf a écrit : Dear all, I've been contemplating whether to submit the attached patch. It addresses an ICE-on-invalid as reported in the PR, and also fixes an accepts-invalid (see testcase), plus maybe some more, related due to incomplete checking of symbo

Re: [PATCH v2] c++: failure to suppress -Wsizeof-array-div in template [PR114983]

On 5/9/24 15:28, Marek Polacek wrote: On Thu, May 09, 2024 at 12:51:28PM -0400, Jason Merrill wrote: On 5/9/24 12:03, Marek Polacek wrote: diff --git a/gcc/cp/pt.cc b/gcc/cp/pt.cc index 8787eabb9fd..46cf8a737fb 100644 --- a/gcc/cp/pt.cc +++ b/gcc/cp/pt.cc @@ -20569,6 +20569,7 @@ tsubst_expr (tr

Re: [PATCH] c++: ICE with reference NSDMI [PR114854]

On 5/9/24 12:04, Marek Polacek wrote: Bootstrapped/regtested on x86_64-pc-linux-gnu, ok for trunk? -- >8 -- Here we crash on a cp_gimplify_expr/TARGET_EXPR assert: /* A TARGET_EXPR that expresses direct-initialization should have been elided by cp_gimplify_init_expr. */

[PATCH v2] c++: failure to suppress -Wsizeof-array-div in template [PR114983]

On Thu, May 09, 2024 at 12:51:28PM -0400, Jason Merrill wrote: > On 5/9/24 12:03, Marek Polacek wrote: > > Bootstrapped/regtested on x86_64-pc-linux-gnu, ok for trunk? > > > > -- >8 -- > > -Wsizeof-array-div offers a way to suppress the warning by wrapping > > the second operand of the division in

Re: [PATCH 1/4] rs6000: Make all 128 bit scalar FP modes have 128 bit precision [PR112993]

On Wed, 8 May 2024, Kewen.Lin wrote: > to widen IFmode to TFmode. To make build_common_tree_nodes > be able to find the correct mode for long double type node, > it introduces one hook mode_for_longdouble to offer target > a way to specify the mode used for long double type node. I don't really

Re: [PATCHv2] Value range: Add range op for __builtin_isfinite

Le 09/05/2024 à 10:47, HAO CHEN GUI a écrit : Hi Mikael, Thanks for your comments. 在 2024/5/9 16:03, Mikael Morin 写道: I think the canonical API behaviour sets R to varying and returns true instead  of just returning false if nothing is known about the range. I'm not sure whether it makes a

Re: [PATCH] c++: Optimize in maybe_clone_body aliases even when not at_eof [PR113208]

On Thu, May 09, 2024 at 02:58:52PM -0400, Marek Polacek wrote: > On Thu, May 09, 2024 at 08:20:00PM +0200, Jakub Jelinek wrote: > > --- gcc/cp/decl.cc.jj 2024-05-09 10:30:54.804505130 +0200 > > +++ gcc/cp/decl.cc 2024-05-09 17:07:08.400110018 +0200 > > @@ -19280,6 +19280,14 @@ cxx_comdat_gro

[committed] testsuite: Fix up pr84508* tests [PR84508]

On Thu, May 09, 2024 at 12:45:42PM +0800, Hongtao Liu wrote: > > PR target/84508 > > * gcc.target/i386/pr84508-1.c: New test. > > * gcc.target/i386/pr84508-2.c: Ditto. The tests FAIL on x86_64-linux with /usr/bin/ld: cannot find -lubsan collect2: error: ld returned 1 exit s

Re: [PATCH] c++: Optimize in maybe_clone_body aliases even when not at_eof [PR113208]

On Thu, May 09, 2024 at 08:20:00PM +0200, Jakub Jelinek wrote: > --- gcc/cp/decl.cc.jj 2024-05-09 10:30:54.804505130 +0200 > +++ gcc/cp/decl.cc2024-05-09 17:07:08.400110018 +0200 > @@ -19280,6 +19280,14 @@ cxx_comdat_group (tree decl) > else > break; > } > + /* If a

[PATCH] c++, mingw, v2: Fix up types of dtor hooks to __cxa_{,thread_}atexit/__cxa_throw on mingw ia32 [PR114968]

On Thu, May 09, 2024 at 01:05:59PM -0400, Jason Merrill wrote: > I think I'd rather pass ob_parm to start_cleanup_fn, where it can also > replace the flag_use_cxa_atexit check in that function. Good idea, changed in the following patch. > > @@ -9998,7 +10004,8 @@ register_dtor_fn (tree decl) > >

Re: [PATCH 3/3] RISC-V: Add memset-zero expansion to cbo.zero

On 5/7/24 11:38 PM, Christoph Müllner wrote: The Zicboz extension offers the cbo.zero instruction, which can be used to clean a memory region corresponding to a cache block. The Zic64b extension defines the cache block size to 64 byte. If both extensions are available, it is possible to use cb

Re: [PATCH 2/3] RISC-V: testsuite: Make cmo tests LTO safe

On 5/7/24 11:38 PM, Christoph Müllner wrote: Let's add '\t' to the instruction match pattern to avoid false positive matches when compiling with -flto. gcc/testsuite/ChangeLog: * gcc.target/riscv/cmo-zicbom-1.c: Add \t to test pattern. * gcc.target/riscv/cmo-zicbom-2.c: Likew

Re: [PATCH 1/3] expr: Export clear_by_pieces()

On 5/7/24 11:38 PM, Christoph Müllner wrote: Make clear_by_pieces() available to other parts of the compiler, similar to store_by_pieces(). gcc/ChangeLog: * expr.cc (clear_by_pieces): Remove static from clear_by_pieces. * expr.h (clear_by_pieces): Add prototype for clear_by_p

[PATCH] c++: Optimize in maybe_clone_body aliases even when not at_eof [PR113208]

On Thu, Apr 25, 2024 at 11:30:48AM -0400, Jason Merrill wrote: > Hmm, maybe maybe_clone_body shouldn't clear DECL_SAVED_TREE for aliases, but > rather set it to some stub like void_node? > > Though with all these changes, it's probably better to go with your first > patch for GCC 14 and delay this

[PATCH] c++: Fix parsing of abstract-declarator starting with ... followed by [ or ( [PR115012]

Hi! The C++26 P2662R3 Pack indexing paper mentions that both GCC and MSVC don't handle T...[10] parameter declaration when T is a pack. While that will change meaning in C++26, in C++11 .. C++23 this ought to be valid. Also, T...(args) as well. The following patch handles those in cp_parser_dir

[PATCH 21/21] diagnostics: fix corrupt json/SARIF on stderr [PR114348]

Various values of -fdiagnostics-format= request machine-readable output on stderr, using JSON, but in various places we use fnotice to write free-form text to stderr, such as "compilation terminated", leading to corrupt JSON. Fix by having fnotice skip the output for such cases. Backported from r

[PATCH 19/21] diagnostics: fix ICE on sarif output when source file is unreadable [PR111700]

Backported from r14-4474-g94caa6a6b4bd73. gcc/ChangeLog: PR driver/111700 * input.cc (file_cache::add_file): Update leading comment to clarify that it can fail. (file_cache::lookup_or_add_file): Likewise. (get_source_file_content): Gracefully handle lookup_o

[PATCH 13/21] analyzer: fix defaults in compound assignments from non-zero offsets [PR112969]

Confusion in binding_cluster::maybe_get_compound_binding about whether offsets are relative to the start of the region or to the start of the cluster was leading to incorrect handling of default values, leading to false positives from -Wanalyzer-use-of-uninitialized-value, from -Wanalyzer-exposure-

[PATCH 10/21] analyzer: fix ICE for 2 bits before the start of base region [PR112889]

Cncrete bindings were using -1 and -2 in the offset field to signify deleted and empty hash slots, but these are valid values, leading to assertion failures inside hash_map::put on a debug build, and probable bugs in a release build. (gdb) call k.dump(true) start: -2, size: 1, next: -1 (gdb) p k.

[PATCH 15/21] analyzer: fix -Wanalyzer-va-arg-type-mismatch false +ve on int types [PR111289]

Backported from commit r14-9076-g5651ad62b08096 (moving new tests from c-c++-common to gcc.dg). gcc/analyzer/ChangeLog: PR analyzer/111289 * varargs.cc (representable_in_integral_type_p): New. (va_arg_compatible_types_p): Add "arg_sval" param. Handle integer types.

[PATCH 18/21] analyzer: fix ICE and false positive with -Wanalyzer-deref-before-check [PR114408]

Backported from commit r14-9646-g80a0cb37456c49 (moving testcase to gcc.dg and handling conflict in kf.cc) gcc/analyzer/ChangeLog: PR analyzer/114408 * engine.cc (impl_run_checkers): Free up any dominance info that we may have created. * kf.cc (class kf_ubsan_handle

[PATCH 03/21] testsuite: Add more allocation size tests for conjured svalues [PR110014]

From: Tim Lange This patch adds the reproducers reported in PR 110014 as test cases. The false positives in those cases are already fixed with PR 109577. 2023-06-09 Tim Lange PR analyzer/110014 gcc/testsuite/ChangeLog: * gcc.dg/analyzer/realloc-pr110014.c: New tests. (cher

[PATCH 11/21] analyzer: fix deref-before-check false positives due to inlining [PR112790]

Backported from commit r14-6918-g5743e1899d5964 (moving testcase from c-c++-common to gcc.dg). gcc/analyzer/ChangeLog: PR analyzer/112790 * checker-event.cc (class inlining_info): Move to... * inlining-iterator.h (class inlining_info): ...here. * sm-malloc.cc: Inclu

[PATCH 20/21] Fix ICE in -fdiagnostics-generate-patch [PR112684]

Backported from r14-8255-ge254d1224df306. gcc/ChangeLog: PR middle-end/112684 * toplev.cc (toplev::main): Don't ICE in -fdiagnostics-generate-patch when exiting after options, since no edit context will have been created. Signed-off-by: David Malcolm --- gcc/topl

[PATCH 16/21] analyzer: fix -Wanalyzer-deref-before-check false positive seen in loop header macro [PR109251]

Backported from commit r14-9586-g9093f275e0a343 (moving tests from c-c++-common to gcc.dg) gcc/analyzer/ChangeLog: PR analyzer/109251 * sm-malloc.cc (deref_before_check::emit): Reject cases where the check is in a loop header within a macro expansion. (deref_before_

[PATCH 09/21] jit: dump string literal initializers correctly

From: Vibhav Pant Signed-off-by: David Malcolm gcc/jit/ChangeLog: * jit-recording.cc (recording::global::write_to_dump): Fix dump of string literal initializers. (cherry picked from commit r14-4923-gac66744d94226a) Signed-off-by: David Malcolm --- gcc/jit/jit-recording.cc |

[PATCH 08/21] testsuite, analyzer: add test case [PR108171]

The ICE in PR analyzer/108171 appears to be a dup of the recently fixed PR analyzer/110882 and is likewise fixed by it; adding this test case. gcc/testsuite/ChangeLog: PR analyzer/108171 * gcc.dg/analyzer/pr108171.c: New test. (cherry picked from commit r14-2957-gf80efa49b7a163)

[PATCH 17/21] analyzer: fix ICE due to type mismatch when replaying call summary [PR114473]

gcc/analyzer/ChangeLog: PR analyzer/114473 * call-summary.cc (call_summary_replay::convert_svalue_from_summary): Assert that the types match. (call_summary_replay::convert_region_from_summary): Likewise. (call_summary_replay::convert_region_from_summa

[PATCH 14/21] analyzer: fix skipping of debug stmts [PR113253]

PR analyzer/113253 reports a case where the analyzer output varied with and without -g enabled. The root cause was that debug stmts were in the FOR_EACH_IMM_USE_FAST list for SSA names, leading to the analyzer's state purging logic differing between the -g and non-debugging cases, and thus leading

[PATCH 02/21] analyzer: Fix allocation size false positive on conjured svalue [PR109577]

From: Tim Lange Currently, the analyzer tries to prove that the allocation size is a multiple of the pointee's type size. This patch reverses the behavior to try to prove that the expression is not a multiple of the pointee's type size. With this change, each unhandled case should be gracefully

[PATCH 07/21] analyzer: fix ICE on zero-sized arrays [PR110882]

gcc/analyzer/ChangeLog: PR analyzer/110882 * region.cc (int_size_in_bits): Fail on zero-sized types. gcc/testsuite/ChangeLog: PR analyzer/110882 * gcc.dg/analyzer/pr110882.c: New test. (cherry picked from commit r14-2955-gc62f93d1e0383d) Signed-off-by: David Malco

[PATCH 05/21] jit.exp: handle dwarf version mismatch in jit-check-debug-info [PR110466]

gcc/testsuite/ChangeLog: PR jit/110466 * jit.dg/jit.exp (jit-check-debug-info): Gracefully handle too early versions of gdb that don't support our dwarf version, via "unsupported". (cherry picked from commit r14-2223-gc3c0ba5436170e) Signed-off-by: David Malcolm -

[PATCH 12/21] analyzer: casting all zeroes should give all zeroes [PR113333]

In particular, accessing the result of *calloc (1, SZ) (if non-NULL) should be known to be all zeroes. (backported from commit r14-7265-gd235bf2e807c5f) gcc/analyzer/ChangeLog: PR analyzer/11 * region-model-manager.cc (region_model_manager::maybe_fold_unaryop): Casting

[PATCH 06/21] analyzer: fix ICE on division of tainted floating-point values [PR110700]

gcc/analyzer/ChangeLog: PR analyzer/110700 * region-model-manager.cc (region_model_manager::get_or_create_int_cst): Assert that we have an integral or pointer type. * sm-taint.cc (taint_state_machine::check_for_tainted_divisor): Don't check non-integr

[PATCH 04/21] jit: avoid using __vector in testcase [PR110466]

r13-4531-gd2e782cb99c311 added test coverage to libgccjit's vector support, but used __vector, which doesn't work on Power. Additionally the size param to gcc_jit_type_get_vector was wrong. Fixed thusly. gcc/testsuite/ChangeLog: PR jit/110466 * jit.dg/test-expressions.c (run_test

[pushed 00/21] Various backports to gcc 13 (analyzer, jit, diagnostics)

I've pushed the following changes to releases/gcc-13 as r13-8741-g89feb3557a0188 through r13-8761-gb7a2697733d19a. Successfully bootstrapped & regrtested on x86_64-pc-linux-gnu. Successful run of analyzer integration tests on x86_64-pc-linux-gnu. Lightly manually tested for patches that didn't hav

[PATCH 01/21] analyzer: add caching to globals with initializers [PR110112]

PR analyzer/110112 notes that -fanalyzer is extremely slow on a source file with large read-only static arrays, repeatedly building the same compound_svalue representing the full initializer, and repeatedly building svalues representing parts of the the full initialiazer. This patch adds caches fo

Re: [PATCH] c++: nested aggregate/alias CTAD fixes

On 5/8/24 13:49, Patrick Palka wrote: Bootstrapped and regtested on x86-64-pc-linux-gnu, does this look OK for trunk and perhaps 14? OK for both. -- >8 -- During maybe_aggr_guide with a nested class template and paren init, like with list init we need to consider the generic template type ra

Re: [PATCH] c++, mingw: Fix up types of dtor hooks to __cxa_{,thread_}atexit/__cxa_throw on mingw ia32 [PR114968]

On 5/9/24 05:01, Jakub Jelinek wrote: Hi! __cxa_atexit/__cxa_thread_atexit/__cxa_throw functions accept function pointers to usually directly destructors rather than wrappers around them. Now, mingw ia32 uses implicitly __attribute__((thiscall)) calling conventions for METHOD_TYPE (where the thi

[PATCH v2 3/3] pretty-print: Don't translate escape sequences to windows console API

Modern versions of windows (after windows 10 v1511) support VT100 escape sequences, so translation for them is not necessary. The translation also mangles embedded warning documentation links. gcc/ChangeLog: * pretty-print.cc (mingw_ansi_fputs): Don't translate escape sequences if

[PATCH v2 2/3] diagnostics: Don't hardcode auto_enable_urls to false for mingw hosts

Windows terminal and mintty both have support for link escape sequences, and so auto_enable_urls shouldn't be hardcoded to false. For older versions of the windows console, mingw_ansi_fputs's console API translation logic does mangle these sequences, but there's nothing useful it could do even if t

[PATCH v2 1/3] diagnostics: Enable escape sequence processing on windows consoles

Since windows 10 release v1511, the windows console has had support for VT100 escape sequences. We should try to enable this, and utilize it where possible. gcc/ChangeLog: * diagnostic-color.cc (should_colorize): Enable processing of VT100 escape sequences on windows consoles Sign

[PATCH 3/3] pretty-print: Don't translate escape sequences to windows console API

Modern versions of windows (after windows 10 v1511) support VT100 escape sequences, so translation for them is not necessary. The translation also mangles embedded warning documentation links. gcc/ChangeLog: * pretty-print.cc (mingw_ansi_fputs): Don't translate escape sequences if

[PATCH 2/3] diagnostics: Don't hardcode auto_enable_urls to false for mingw hosts

Windows terminal and mintty both have support for link escape sequences, and so auto_enable_urls shouldn't be hardcoded to false. For older versions of the windows console, mingw_ansi_fputs's console API translation logic does mangle these sequences, but there's nothing useful it could do even if t

[PATCH 1/3] diagnostics: Enable escape sequence processing on windows consoles

Since windows 10 release v1511, the windows console has had support for VT100 escape sequences. We should try to enable this, and utilize it where possible. gcc/ChangeLog: * diagnostic-color.cc (should_colorize): Enable processing of VT100 escape sequences on windows consoles Sign

Re: [PATCH] c++: failure to suppress -Wsizeof-array-div in template [PR114983]

On 5/9/24 12:03, Marek Polacek wrote: Bootstrapped/regtested on x86_64-pc-linux-gnu, ok for trunk? -- >8 -- -Wsizeof-array-div offers a way to suppress the warning by wrapping the second operand of the division in parens: sizeof (samplesBuffer) / (sizeof(unsigned char)) but this doesn't wor

Re: [PATCH 2/4] fortran: Teach get_real_kind_from_node for Power 128 fp modes [PR112993]g

On Thu, May 09, 2024 at 01:37:32PM +0800, Kewen.Lin wrote: > > > > > That said, Fortran has the concept of model numbers, which > > are set in arith.c. Does this change give the expected > > value for ibm128? For example, with "REAL(16) X", one > > has "DIGITS(X) = 113", which is the precision

Re: [PATCH] c++: DR 569, DR 1693: fun with semicolons [PR113760]

On 5/9/24 12:16, Marek Polacek wrote: In GCC 14, I submitted a minimal fix for the "extra ; warning", pushed in r14-8967. That patch mentions a more complete patch for GCC 15. This is the patch. Bootstrapped/regtested on x86_64-pc-linux-gnu, ok for trunk? -- >8 -- Prompted by c++/113760, I sta

[PATCH] c++: DR 569, DR 1693: fun with semicolons [PR113760]

In GCC 14, I submitted a minimal fix for the "extra ; warning", pushed in r14-8967. That patch mentions a more complete patch for GCC 15. This is the patch. Bootstrapped/regtested on x86_64-pc-linux-gnu, ok for trunk? -- >8 -- Prompted by c++/113760, I started looking into a bogus "extra ;" warn

Re: [PATCH v22 20/23] c++: Implement __is_invocable built-in trait

On 5/8/24 01:04, Ken Matsui wrote: Fixed the reference_wrapper case. I used non_ref_datum_type to avoid potentially multiple build_trait_object calls. -- >8 -- This patch implements built-in trait for std::is_invocable. gcc/cp/ChangeLog: * cp-trait.def: Define __is_invocable.

[PATCH] c++: ICE with reference NSDMI [PR114854]

Bootstrapped/regtested on x86_64-pc-linux-gnu, ok for trunk? -- >8 -- Here we crash on a cp_gimplify_expr/TARGET_EXPR assert: /* A TARGET_EXPR that expresses direct-initialization should have been elided by cp_gimplify_init_expr. */ gcc_checking_assert (!TARGET_EXPR_DIRECT_I

[PATCH] c++: failure to suppress -Wsizeof-array-div in template [PR114983]

Bootstrapped/regtested on x86_64-pc-linux-gnu, ok for trunk? -- >8 -- -Wsizeof-array-div offers a way to suppress the warning by wrapping the second operand of the division in parens: sizeof (samplesBuffer) / (sizeof(unsigned char)) but this doesn't work in a template, because we fail to propa

Re: [PATCH 1/3] diagnostics: Enable escape sequence processing on windows consoles

在 2024-05-09 22:48, Peter Damianov 写道: - h = GetStdHandle (STD_ERROR_HANDLE); - return (h != INVALID_HANDLE_VALUE) && (h != NULL) - && GetConsoleMode (h, &m); + handle = GetStdHandle (STD_ERROR_HANDLE); + isconsole = GetConsoleMode (handle, &mode); Shouldn't `GetConsoleMode()` be ca

[PATCH] Add myself to DCO

I am retiring from Intel. Friday, May 10 is my last day. I will submit my GCC, glibc and binutils patches under DCO from now on. H.J. ChangeLog: * MAINTAINERS: Add myself to DCO. Signed-off-by: H.J. Lu --- MAINTAINERS | 1 + 1 file changed, 1 insertion(+) diff --git a/MAINTAIN

Re: [PATCH 00/23] prange: pointer ranges

> Tested and benchmarked on x86-64 Linux. Why aren't these patches being tested on all major architectures, especially those available in the Compile Farm? At least for correctness, if not performance. Thanks, David

Re: [PATCH 2/2] RISC-V: Add cmpmemsi expansion

On 5/7/24 11:52 PM, Christoph Müllner wrote: GCC has a generic cmpmemsi expansion via the by-pieces framework, which shows some room for target-specific optimizations. E.g. for comparing two aligned memory blocks of 15 bytes we get the following sequence: my_mem_cmp_aligned_15: li

[PATCH 3/3] pretty-print: Don't translate escape sequences to windows console API

Modern versions of windows (after windows 10 v1511) support VT100 escape sequences, so translation for them is not necessary. The translation also mangles embedded warning documentation links. gcc/ChangeLog: * pretty-print.cc (mingw_ansi_fputs): Don't translate escape sequences if

[PATCH 1/3] diagnostics: Enable escape sequence processing on windows consoles

Since windows 10 release v1511, the windows console has had support for VT100 escape sequences. We should try to enable this, and utilize it where possible. gcc/ChangeLog: * diagnostic-color.cc (should_colorize): Enable processing of VT100 escape sequences on windows consoles Sign

[PATCH 2/3] diagnostics: Don't hardcode auto_enable_urls to false for mingw platforms

Windows terminal and mintty both have support for link escape sequences, and so should follow the same detection logic as the rest of the hosts. With conhost.exe, the embedded URLs are not supported, but it doesn't cause any problems to print them. gcc/ChangeLog: * diagnostic-color.cc (aut

New German PO file for 'gcc' (version 14.1.0)

Hello, gentle maintainer. This is a message from the Translation Project robot. A revised PO file for textual domain 'gcc' has been submitted by the German team of translators. The file is available at: https://translationproject.org/latest/gcc/de.po (This file, 'gcc-14.1.0.de.po', has jus

[COMMITTED][GCC13] Backport of 111009 patch.

As requested, backported the patch for 111009 to resolve incorrect ranges from addr_expr and committed to GCC 13 branch. bootstraps and passes all tests on x86_64-pc-linux-gnu Andrew commit 7a0b2d5aad263beb9babebf2b96c9660d090607e Author: Andrew MacLeod Date: Wed May 8 10:22:23 2024 -0400

New German PO file for 'gcc' (version 14.1.0)

Hello, gentle maintainer. This is a message from the Translation Project robot. A revised PO file for textual domain 'gcc' has been submitted by the German team of translators. The file is available at: https://translationproject.org/latest/gcc/de.po (This file, 'gcc-14.1.0.de.po', has jus

RE: [pushed][PR114810][LRA]: Recognize alternatives with lack of available registers for insn and demote them.

Sure thing, see below PR. https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115013 Pan From: Vladimir Makarov Sent: Thursday, May 9, 2024 8:21 PM To: Li, Pan2 ; gcc-patches@gcc.gnu.org Subject: Re: [pushed][PR114810][LRA]: Recognize alternatives with lack of available registers for insn and demote

[r15-337 Regression] FAIL: gcc.target/i386/pr84508-2.c (test for excess errors) on Linux/x86_64

On Linux/x86_64, 5967696c0f6300da4387fea5d102be5bc9f23233 is the first bad commit commit 5967696c0f6300da4387fea5d102be5bc9f23233 Author: Hu, Lin1 Date: Fri Jan 19 15:22:10 2024 +0800 i386: Fix some intrinsics without alignment requirements. caused FAIL: gcc.target/i386/pr84508-1.c (test

New French PO file for 'gcc' (version 14.1.0)

Hello, gentle maintainer. This is a message from the Translation Project robot. A revised PO file for textual domain 'gcc' has been submitted by the French team of translators. The file is available at: https://translationproject.org/latest/gcc/fr.po (This file, 'gcc-14.1.0.fr.po', has jus

Re: [pushed][PR114810][LRA]: Recognize alternatives with lack of available registers for insn and demote them.

On 5/8/24 23:25, Li, Pan2 wrote: Hi Vladimir, Looks this patch results in some ICE in the rvv.exp of RISC-V backend, feel free to ping me if more information is needed for reproducing. = Summary of gcc testsuite = | # of unexpected case / # of unique unexpected case |gcc |

[Patch, aarch64] v3: Preparatory patch to place target independent and,dependent changed code in one file

Hello Alex/Richard: All review comments are addressed. Common infrastructure of load store pair fusion is divided into target independent and target dependent changed code. Target independent code is the Generic code with pure virtual function to interface betwwen target independent and dependen

test mail

Re: gcc/DATESTAMP wasn't updated since 20240507

On Thu, May 09, 2024 at 12:14:43PM +0200, Jakub Jelinek wrote: > On Thu, May 09, 2024 at 12:04:38PM +0200, Rainer Orth wrote: > > I just noticed that gcc/DATESTAMP wasn't updated yesterday and today, > > staying at 20240507. > > I think it is because of the r15-268 commit, we do support > This rev

RE: [PATCH v1] RISC-V: Make full-vec-move1.c test robust for optimization

Committed, thanks Juzhe. Pan From: juzhe.zh...@rivai.ai Sent: Thursday, May 9, 2024 5:05 PM To: Li, Pan2 ; gcc-patches Cc: kito.cheng ; Li, Pan2 Subject: Re: [PATCH v1] RISC-V: Make full-vec-move1.c test robust for optimization lgtm juzhe.zh...@rivai.ai

Ping: [PATCH v3] doc: Correction of Tree SSA Passes info.

Ping. Is this version of patch ok for trunk? thanks! On 2024/3/26 09:54, Chenghui Pan wrote: Current document of Tree SSA passes contains many parts that is not updated for many years. This patch removes some info that is outdated and not existed in current GCC codebase, and fixes some wrong co

Re: [PATCH, aarch64] v2: Preparatory patch to place target independent and,dependent changed code in one file

Hello Alex: On 08/05/24 6:18 pm, Alex Coplan wrote: > Hi Ajit, > > Sorry for the long delay in reviewing this. > > This is really getting there now. I've left a few more comments below. > > Apart from minor style things, the main remaining issues are mostly > around comments. It's important t

Re: gcc/DATESTAMP wasn't updated since 20240507

On Thu, May 09, 2024 at 12:04:38PM +0200, Rainer Orth wrote: > I just noticed that gcc/DATESTAMP wasn't updated yesterday and today, > staying at 20240507. I think it is because of the r15-268 commit, we do support This reverts commit ... when the referenced commit contains a ChangeLog message, bu

gcc/DATESTAMP wasn't updated since 20240507

I just noticed that gcc/DATESTAMP wasn't updated yesterday and today, staying at 20240507. Rainer -- - Rainer Orth, Center for Biotechnology, Bielefeld University

Re: [COMMITTED] Enable prange support.

This is: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114985 I have proposed a patch but need confirmation from the IPA folks. Aldy On Thu, May 9, 2024 at 10:08 AM Andreas Schwab wrote: > > Breaks bootstrap on aarch64. > > $ /opt/gcc/gcc-20240509/Build/./prev-gcc/xg++ >

[committed] testsuite: Fix up vector-subaccess-1.C test for ia32 [PR89224]

Hi! The test FAILs on i686-linux due to .../gcc/testsuite/g++.dg/torture/vector-subaccess-1.C:16:6: warning: SSE vector argument without SSE enabled changes the ABI [-Wpsabi] excess warnings. This fixes it by adding -Wno-psabi, like commonly done in other tests. Committed to trunk as obvious af

  1   2   >