On 4/28/23 11:23, Florian Weimer wrote:
> * Martin Liška:
>
>> On 4/26/23 20:31, Florian Weimer wrote:
>>> * Martin Liška:
>>>
>>>> On 11/15/22 16:47, Martin Liška wrote:
>>>>> Hi.
>>>>>
>>>>> I've just
On 4/26/23 20:31, Florian Weimer wrote:
> * Martin Liška:
>
>> On 11/15/22 16:47, Martin Liška wrote:
>>> Hi.
>>>
>>> I've just pushed libsanitizer update that was tested on x86_64-linux and
>>> ppc64le-linux systems.
>>> Moreover, I
On 4/26/23 21:23, H.J. Lu wrote:
> On Wed, Apr 26, 2023 at 6:52 AM Martin Liška wrote:
>>
>> On 11/15/22 16:47, Martin Liška wrote:
>>> Hi.
>>>
>>> I've just pushed libsanitizer update that was tested on x86_64-linux and
>>> ppc64le-linu
On 11/15/22 16:47, Martin Liška wrote:
> Hi.
>
> I've just pushed libsanitizer update that was tested on x86_64-linux and
> ppc64le-linux systems.
> Moreover, I run bootstrap on x86_64-linux and checked ABI difference with
> abidiff.
Hello.
And I've done the
On 1/20/23 18:33, Jason Merrill wrote:
> Martin, I wonder about having the hooks reject out-of-order CommitDate
> in future?
Yes, I would do that. Looking at the last 30K commmits I see just a few
violations
of the order:
UNIXTS hash
1668298622 30d77d49628
1630019619 5889e842ae4
1626967834 3
Hi.
I've just pushed libsanitizer update that was tested on x86_64-linux and
ppc64le-linux systems.
Moreover, I run bootstrap on x86_64-linux and checked ABI difference with
abidiff.
Pushed as r13-4068-g3037f11fb86eda.
Cheers,
Martin
On 11/15/22 11:07, Jakub Jelinek wrote:
> On Tue, Nov 15, 2022 at 11:02:53AM +0100, Martin Liška wrote:
>>> Is it allowed to merge libsanitizer from LLVM in stage 3? If not I'd
>>> like to cherry pick some commits from LLVM [to fix some stupid errors
>>
On 11/14/22 18:21, Xi Ruoyao wrote:
> Hi Martin,
>
Hello.
> Is it allowed to merge libsanitizer from LLVM in stage 3? If not I'd
> like to cherry pick some commits from LLVM [to fix some stupid errors
> I've made in LoongArch libasan :(].
I'm sorry but I was really busy with the porting of the
On 10/18/22 14:22, Ben Boeckel wrote:
> On Thu, Oct 13, 2022 at 13:08:46 -0400, David Malcolm wrote:
>> On Mon, 2022-10-10 at 16:21 -0400, Jason Merrill wrote:
>>> David Malcolm would probably know best about JSON wrangling.
>>
>> Unfortunately our JSON output doesn't make any guarantees about the
On 9/20/22 14:17, Tobias Burnus wrote:
> Hi Martin,
>
> On 20.09.22 14:02, Martin Liška wrote:
>> diff --git a/gcc/fortran/gfortran.texi b/gcc/fortran/gfortran.texi
>> @@ -455,9 +455,7 @@ version 2.6, @uref{https://www.openacc.org/}). See
>> The Fortran 95 standard s
PR fortran/106636
gcc/fortran/ChangeLog:
* gfortran.texi: Remove 2 dead links.
---
gcc/fortran/gfortran.texi | 4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
diff --git a/gcc/fortran/gfortran.texi b/gcc/fortran/gfortran.texi
index 59d673bfc03..25410e6088d 100644
--- a/gc
On 1/18/22 20:10, Harald Anlauf via Fortran wrote:
Am 17.01.22 um 22:26 schrieb Martin Liška:
On 1/12/22 16:54, Martin Liška wrote:
There's a patch that enhances git-backport so that it updates commit
messages for files which name ends now with .cc and is still .c on a branch.
The patc
On 1/12/22 16:54, Martin Liška wrote:
There's a patch that enhances git-backport so that it updates commit
messages for files which name ends now with .cc and is still .c on a branch.
The patch has been installed as I've made the renaming now.
Cheers,
Martin
On 1/14/22 08:44, Bernhard Reutner-Fischer wrote:
On Wed, 12 Jan 2022 16:54:46 +0100
Martin Liška wrote:
+def replace_file_in_changelog(lines, filename):
+if not filename.endswith('.cc'):
+return
+
+# consider all componenets of a path: gcc/ipa-icf.cc
+whil
Hi.
There's a patch that enhances git-backport so that it updates commit
messages for files which name ends now with .cc and is still .c on a branch.
Example usage:
$ git show test
commit 8ed4b2cb9aa158c0ef418fd1ac66271664904604 (test)
Author: Martin Liska
Date: Wed Jan 12 16:08:13 2022 +010
On 1/11/22 17:16, Jakub Jelinek wrote:
On Tue, Jan 11, 2022 at 05:03:34PM +0100, Martin Liška wrote:
On 1/11/22 16:56, Jakub Jelinek wrote:
While e.g. libcpp or gcc are in C++.
Which means I should rename .c files under libcpp, right?
Is there any other folder from gcc/ and libcpp/ that
On 1/11/22 16:56, Jakub Jelinek wrote:
While e.g. libcpp or gcc are in C++.
Which means I should rename .c files under libcpp, right?
Is there any other folder from gcc/ and libcpp/ that would need that as well?
Martin
On 1/11/22 16:48, Toon Moene wrote:
On 1/11/22 13:56, Martin Liška wrote:
Patch can bootstrap on x86_64-linux-gnu and survives regression tests.
Plus it survives build of all FEs (--enable-languages=all) on x86_64-linux-gnu
and I've built all cross compilers.
Does this also rename .c
On 12/14/21 01:22, Manfred Schwarb wrote:
Am 13.12.21 um 13:29 schrieb Martin Liška:
On 12/13/21 12:18, Manfred Schwarb via Fortran wrote:
could you commit it for me? I do not have commit access.
I can definitely do that, but please attach the patches as output of git
format-patch
so that
On 12/13/21 12:18, Manfred Schwarb via Fortran wrote:
could you commit it for me? I do not have commit access.
I can definitely do that, but please attach the patches as output of git
format-patch
so that git am can be directly used.
Cheers,
Martin
Hello.
The function was introduced in 2009 in
g:cf2b3c22a2cbd7f50db530ca9d2b14c70ba0359d
and has never been used since that.
Ready to be installed?
Thanks,
Martin
gcc/fortran/ChangeLog:
* symbol.c (gfc_get_ultimate_derived_super_type): Remove.
---
gcc/fortran/symbol.c | 17 --
On 11/2/21 16:56, Sandra Loosemore wrote:
On 11/2/21 9:20 AM, Martin Liška wrote:
On 11/2/21 15:48, Sandra Loosemore wrote:
On 11/2/21 2:51 AM, Martin Liška wrote:
On 11/2/21 00:56, Sandra Loosemore wrote:
I'll wait a couple days before committing these patches, in case
anybody wants to
On 11/2/21 15:48, Sandra Loosemore wrote:
On 11/2/21 2:51 AM, Martin Liška wrote:
On 11/2/21 00:56, Sandra Loosemore wrote:
I'll wait a couple days before committing these patches, in case
anybody wants to give some feedback, especially on technical issues.
Hello.
Appreciate the wor
On 11/2/21 00:56, Sandra Loosemore wrote:
I'll wait a couple days before committing these patches, in case
anybody wants to give some feedback, especially on technical issues.
Hello.
Appreciate the work you did, but the patchset will cause quite some conflicts
in the prepared Sphinx migration
Hello.
Can please anybody help me with a Fotran issue, where 'ENTRY' keyword causes
having a function which ends on a smaller line number than it starts:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102460#c7
Thanks,
Martin
Hello.
I noticed the patch causes the following clang warnings:
gcc/fortran/dump-parse-tree.c:1786:11: warning: comparison of different
enumeration types in switch statement ('enum gfc_omp_defaultmap' and
'gfc_omp_defaultmap_category') [-Wenum-compare-switch]
gcc/fortran/dump-parse-tree.c:1787
Pushed as obvious.
Martin
gcc/fortran/ChangeLog:
* intrinsic.texi: Add missing @headitem to tables with a header.
---
gcc/fortran/intrinsic.texi | 144 ++---
1 file changed, 72 insertions(+), 72 deletions(-)
diff --git a/gcc/fortran/intrinsic.texi b/gcc
from a good location. I'm going to improve it.
Cheers,
Martin
Thanks for your help,
Andre
On Sat, 22 May 2021 19:58:57 +0200
Martin Liška wrote:
On 5/22/21 1:39 PM, Andre Vehreschild via Gcc-patches wrote:
Hi Steve and Jerry,
thanks for the ok'ing.
On 5/22/21 1:39 PM, Andre Vehreschild via Gcc-patches wrote:
Hi Steve and Jerry,
thanks for the ok'ing.
Committed as https://gcc.gnu.org/g:26ca6dbda23bc6dfab96ce07afa70ebacedfaf9c
and https://gcc.gnu.org/g:c4771b3438a8cd9afcef1762957b763f8df3fa6e (for the
missing changelog entries).
Hello.
A
A column with empty values seems suspicious.
Ready to be installed?
Thanks,
Martin
gcc/fortran/ChangeLog:
* intrinsic.texi: The table has first column empty and it makes
trouble when processing makeinfo --xml output.
---
gcc/fortran/intrinsic.texi | 18 +-
1 file
30 matches
Mail list logo
