On 20 May 2024 02:31:27 CEST, Sandra Loosemore wrote:
>On 5/19/24 02:01, Tobias Burnus wrote:
>> I noticed that gfortran's coarray support did not link to the
>> http://www.opencoarrays.org/ >
>> [snip]
>>
>> diff --git a/gcc/fortran/invoke.texi b/gcc/fortran/invoke.texi
>> index
On 12 April 2024 07:30:10 CEST, HAO CHEN GUI wrote:
>
>
>patch.diff
>diff --git a/gcc/gimple-range-op.cc b/gcc/gimple-range-op.cc
>index 9de130b4022..99c511728d3 100644
>--- a/gcc/gimple-range-op.cc
>+++ b/gcc/gimple-range-op.cc
>@@ -1192,6 +1192,56 @@ public:
> }
> } op_cfn_isinf;
>
On 5 April 2024 03:03:05 CEST, "H.J. Lu" wrote:
>On Thu, Apr 4, 2024 at 5:34 PM wrote:
>>
>> On 3 April 2024 15:49:13 CEST, "H.J. Lu" wrote:
>
>> + /* Skip if it has been visited. */
>> + unsigned int uid = e->caller->get_uid ();
>> + if (bitmap_bit_p (ifunc_ref_map, uid))
>> +
On 3 April 2024 15:49:13 CEST, "H.J. Lu" wrote:
>> OK witht that change.
>> Honza
>
>I am checking in this patch with the updated comments:
>
> /* Disable indirect call profiling for an IFUNC resolver and its
> callees since it requires TLS which hasn't been set up yet when
> the
On 19 March 2024 18:27:13 CET, Kaz Kylheku wrote:
>On 2024-03-18 00:30, Jonathan Wakely wrote:
>> I don't have an opinion on the implementation, or the proposal itself,
>> except that the implementation seems susprisingly simple, which is
>> nice.
>
>Hi Jonathan,
>
>Here is an updated patch.
>
On 19 March 2024 14:40:57 CET, Christophe Lyon
wrote:
>On Mon, 18 Mar 2024 at 22:35, Evgeny Karpov
>wrote:
>>
>> Monday, March 18, 2024 2:27 PM
>> Christophe Lyon wrote:
>>
>> > > +/* Disable SEH and declare the required SEH-related macros that are
>> > > +still needed for compilation. */
On 5 March 2024 04:15:12 CET, Jerry D wrote:
>
>Attached is the revised patch using the already available string_len_trim
>function.
>
>This hunk is only executed if a user has not passed an iostat or iomsg
>variable in the parent I/O statement and an error is triggered which
>terminates
On 23 February 2024 22:15:17 CET, Harald Anlauf wrote:
>Hi Steve, all,
>
>here's an updated patch with an enhanced testcase that also
>checks MOLD= besides SOURCE=.
>
>Regtested on x86_64-pc-linux-gnu. Is it OK for mainline?
LGTM
cheers
>
>Cheers,
>Harald
On 21 February 2024 19:34:43 CET, Evgeny Karpov
wrote:
>
Please use git send-email. Your mail ends up as empty as here, otherwise.
The ChangeLog has to be expressed in present tense, as mandated by the
standard; s/Moved/Move/g etc.
In any sane world ( and in gcc ) to fold, respectively a
On 21 February 2024 18:16:30 CET, David Faust wrote:
>
>
>On 2/20/24 02:24, Cupertino Miranda wrote:
>> gcc/ChangeLog:
>> * config.gcc (target_gtfiles): changed coreout to btfext-out.
>> (extra_objs): changed coreout to btfext-out.
>
>I think these entries should start with a capital
On 5 February 2024 12:30:23 CET, Christophe Lyon
wrote:
>On Fri, 2 Feb 2024 at 11:40, Christophe Lyon
>wrote:
>>
>> On Fri, 2 Feb 2024 at 11:10, wrote:
>> >
>> > On 1 February 2024 18:15:34 CET, Christophe Lyon
>> > wrote:
>> > >BUILD_INFO is currently a byproduct of checking makeinfo
>> >
On 2 February 2024 00:02:54 CET, "H.J. Lu" wrote:
>On Thu, Feb 1, 2024 at 10:32 AM Jakub Jelinek wrote:
>>
>> On Thu, Feb 01, 2024 at 10:15:30AM -0800, H.J. Lu wrote:
>> > --- a/gcc/config/i386/i386.cc
>> > +++ b/gcc/config/i386/i386.cc
>> > @@ -22749,6 +22749,31 @@ current_fentry_section (const
On 1 February 2024 18:15:34 CET, Christophe Lyon
wrote:
>BUILD_INFO is currently a byproduct of checking makeinfo
>presence/version. INSTALL_INFO used to be defined similarly, but was
>removed in 2000 (!) by commit 17db658241d18cf6db59d31bc2d6eac96e9257df
>(svn r38141).
>
>In order to save
On 29 January 2024 22:06:04 CET, Harald Anlauf wrote:
>Am 29.01.24 um 21:45 schrieb Bernhard Reutner-Fischer:
>> On Wed, 17 Nov 2021 21:32:14 +0100
>> Harald Anlauf wrote:
>>
>>> Do you have testcases/reproducers demonstrating that the patch actually
>>> fixes the issues you're describing?
>>
On 28 January 2024 22:43:37 CET, Steve Kargl
wrote:
>On Sun, Jan 28, 2024 at 08:56:24PM +0100, Harald Anlauf wrote:
>>
>> Am 28.01.24 um 12:39 schrieb Mikael Morin:
>> > Le 24/01/2024 à 22:39, Harald Anlauf a écrit :
>> > > Dear all,
>> > >
>> > > this patch is actually only a followup fix to
On 24 January 2024 20:30:45 CET, Andi Kleen wrote:
>---
> gcc/doc/extend.texi | 16
> 1 file changed, 16 insertions(+)
>
>diff --git a/gcc/doc/extend.texi b/gcc/doc/extend.texi
>index 0bc586d120e7..c68d32bed8de 100644
>--- a/gcc/doc/extend.texi
>+++ b/gcc/doc/extend.texi
>@@
On 22 January 2024 21:33:17 CET, Kwok Cheung Yeung
wrote:
>Hi
>
>There was a bug in the declare-target-indirect-2.c libgomp testcase (testing
>indirect calls in offloaded target regions, spread over multiple
>teams/threads) that due to an errant fallthrough in a switch statement
>resulted in
On 17 January 2024 14:20:49 CET, Jan Hubicka wrote:
>--- a/gcc/predict.def
>+++ b/gcc/predict.def
>@@ -94,6 +94,16 @@ DEF_PREDICTOR (PRED_LOOP_ITERATIONS_GUESSED, "guessed loop
>iterations",
> DEF_PREDICTOR (PRED_LOOP_ITERATIONS_MAX, "guessed loop iterations",
> PROB_UNINITIALIZED,
Hi
Just another commentary typo..
On 17 January 2024 11:23:01 CET, Jakub Jelinek wrote:
>--- gcc/gengtype.cc.jj 2024-01-03 11:51:23.314845233 +0100
>+++ gcc/gengtype.cc2024-01-16 18:56:57.383009291 +0100
>@@ -4718,8 +4718,8 @@ write_roots (pair_p variables, bool emit
> }
>
> /* Prints
On 19 January 2024 03:41:57 CET, Kito Cheng wrote:
>Thanks, pushed to trunk :)
Thanks, but don't you have to update the tests too, at least
gcc/testsuite/gcc.target/riscv/rvv/base/big_endian-2.c ?
thanks
>
>On Fri, Jan 19, 2024 at 10:36 AM juzhe.zh...@rivai.ai
> wrote:
>>
>> OK
>>
>>
On 11 January 2024 10:59:21 CET, YunQiang Su wrote:
>Fix build warning:
> mips.cc: warning: unused parameter 'decl'.
>
>gcc
> * config/mips/mips.cc (mips_start_function_definition):
> Add ATTRIBUTE_UNUSED.
>---
> gcc/config/mips/mips.cc | 3 ++-
> 1 file changed, 2 insertions(+), 1
On 27 November 2023 15:48:33 CET, Thomas Schwinge
wrote:
>Hi!
>
>On 2023-10-28T21:19:59+0200, Samuel Thibault wrote:
>> We need the multilib paths in gcc to find e.g. glibc crt files on
>> Debian.
>
>ACK.
>
>> This is essentially based on t-linux64 version.
>
>Yes, but isn't the overall setup
On 22 November 2023 23:23:41 CET, Jeff Law wrote:
>
>
>On 11/20/23 11:56, Dimitar Dimitrov wrote:
>> On Sun, Nov 19, 2023 at 05:47:56PM -0700, Jeff Law wrote:
>> ...
>>> + enum rtx_code xcode = GET_CODE (x);
>>> + if (xcode == SET)
>>> + {
>>> + const_rtx dst = SET_DEST (x);
>>>
On 3 November 2023 14:38:06 CET, Jeff Law wrote:
>
>
>On 11/3/23 06:54, Maxim Kuvyrkov wrote:
>> gotools/ChangeLog:
>>
>> * Makefile.am: Update "Running ..." output
>> * Makefile.in: Regenerate.
>OK. Thanks for running down the differences in the autogenerated bits.
Many thanks
On 2 November 2023 11:25:47 CET, Jonathan Wakely wrote:
>On Thu, 2 Nov 2023 at 10:23, Andreas Schwab wrote:
>>
>> On Nov 02 2023, Jonathan Wakely wrote:
>>
>> > Git tags are cheap, but I can imagine a concern about hundreds of new
>> > tags "littering" the output of 'git tag -l'. I don't _think_
On 2 November 2023 18:06:54 CET, Maxim Kuvyrkov
wrote:
>> On Nov 2, 2023, at 21:02, rep.dot@gmail.com wrote:
>>
>> Hi Maxim!
>>
>> Many thanks for the patch! Quick question below..
>>
>> On 2 November 2023 13:48:55 CET, Maxim Kuvyrkov
>> wrote:
>>> ... to restore compatability with
Hi Maxim!
Many thanks for the patch! Quick question below..
On 2 November 2023 13:48:55 CET, Maxim Kuvyrkov
wrote:
>... to restore compatability with validate_failures.py .
>The testsuite script validate_failures.py expects
>"Running ..." to extract values,
>and gotools.sum provided "Running
On 24 October 2023 09:36:22 CEST, Ajit Agarwal wrote:
>Hello Bernhard:
>
>On 23/10/23 7:40 pm, Bernhard Reutner-Fischer wrote:
>> On Mon, 23 Oct 2023 12:16:18 +0530
>> Ajit Agarwal wrote:
>>
>>> Hello All:
>>>
>>> Addressed below review comments in the version 11 of the patch.
>>> Please review
On 24 October 2023 21:25:01 CEST, Harald Anlauf wrote:
>Dear all,
>
>the attached simple patch adds a forgotten check that an event handle
>cannot be a coarray. This case appears to have been overlooked in the
>original fix for this PR.
>
>I intend to commit as obvious within 24h unless there
On 22 October 2023 21:45:12 CEST, Jeff Law wrote:
>
>
>On 10/22/23 10:09, Andrew Pinski wrote:
>> On Sun, Oct 22, 2023 at 12:47 AM Florian Weimer wrote:
>>>
>>> Current glibc headers only declare fputs_unlocked for _GNU_SOURCE.
>>> Defining the macro avoids an implicit function declaration.
>>
On 21 October 2023 01:56:16 CEST, Vineet Gupta wrote:
>On 10/19/23 23:50, Ajit Agarwal wrote:
>> Hello All:
>>
>> This version 9 of the patch uses abi interfaces to remove zero and sign
>> extension elimination.
>> Bootstrapped and regtested on powerpc-linux-gnu.
>>
>> In this version (version
On 12 October 2023 14:35:36 CEST, Ajit Agarwal wrote:
>This patch improves code sinking pass to sink statements before call to reduce
>register pressure.
>Review comments are incorporated.
Typo: "block block"
And spurious whitespace changes.
On 27 September 2023 16:47:27 CEST, Maxim Kuvyrkov
wrote:
>Hi Bernhard,
>
>Thanks, I meant to fix this, but forgot.
np.
>The underlying problem here is that we want to detect which sub-testsuites had
>failures. Current regex doesn't match go's case because there is no "..." at
>the end:
33 matches
Mail list logo
