Hi,
We, EPI, SiPearl, and SiFive, have come out with a RFC for RISC-V
vector intrinsics. If you are interested in the RISC-V vector
intrinsics design, welcome to join the discussion. We have created a
github repository[0] for the documents.
In this RFC[1], we defined the type system, programming
I got:
$ git push origin releases/gcc-10
Enumerating objects: 15, done.
Counting objects: 100% (15/15), done.
Delta compression using up to 8 threads
Compressing objects: 100% (6/6), done.
Writing objects: 100% (8/8), 1.15 KiB | 1.15 MiB/s, done.
Total 8 (delta 7), reused 2 (delta 2), pack-reused
On 5/19/20 3:38 AM, Florian Weimer via Gcc wrote:
> One minor improvement would be to document __aarch64_have_lse_atomics as
> interposable on the GCC side and define that directly in glibc, so that
> lse-init.o is not linked in anymore and __aarch64_have_lse_atomics can
> be initialized as soon as
On Tue, 19 May 2020 at 23:19, Jonathan Wakely wrote:
>
> On Tue, 19 May 2020 at 11:44, Martin Liška wrote:
> >
> > Hello.
> >
> > We've just installed server git hooks that verify git messages
> > for a correct ChangeLog format. For a limited time period, please
> > still apply ChangeLog changes
On Tue, 19 May 2020 at 11:44, Martin Liška wrote:
>
> Hello.
>
> We've just installed server git hooks that verify git messages
> for a correct ChangeLog format. For a limited time period, please
> still apply ChangeLog changes to the corresponding ChangeLog files.
> We'll use it for comparison of
Hello,
On Tue, 19 May 2020, Jakub Jelinek wrote:
> On Tue, May 19, 2020 at 05:21:16PM +0100, Richard Earnshaw wrote:
> > This is really a wart in the GNU coding style. And one reason why I
> > tend to indent such labels by a single space. It particularly affects
> > things like class definition
On Tue, 19 May 2020 at 09:26, Jakub Jelinek via Gcc wrote:
>
> On Tue, May 19, 2020 at 10:11:28AM +0200, Martin Liška wrote:
> > > I find this format more helpful for the reasons below so unless your
> > > script can be tweaked to do something similar I'd like to be able to
> > > continue to use m
On Tue, 19 May 2020 at 17:13, Joseph Myers wrote:
>
> On Tue, 19 May 2020, Martin Liška wrote:
>
> > On 5/19/20 10:11 AM, Martin Liška wrote:
> > > Can you please share how do you do it? It would be easy to add it.
> >
> > I added the feature via --fill-up-bug-titles option. It uses common
> > requ
On 5/19/20 1:26 PM, Martin Liška wrote:
On 5/19/20 9:19 PM, Martin Sebor via Gcc wrote:
Yep, that was it. It's one of those things that you can stare at
for minutes before you notice it.
Thank you for the report, it's 1:0 for the hook ;)
Next time, please CC me to a similar issue with the hoo
On 5/19/20 9:19 PM, Martin Sebor via Gcc wrote:
Yep, that was it. It's one of those things that you can stare at
for minutes before you notice it.
Thank you for the report, it's 1:0 for the hook ;)
Next time, please CC me to a similar issue with the hook.
Martin
On 5/19/20 1:11 PM, Marek Polacek wrote:
On Tue, May 19, 2020 at 01:03:09PM -0600, Martin Sebor via Gcc wrote:
I'm having trouble with the commit hook that tries to enforce
ChangeLog contents. It fails with an error that doesn't make
sense to me: the file it complains isn't mentioned clearly is
On 5/19/20 1:03 PM, Martin Sebor wrote:
I'm having trouble with the commit hook that tries to enforce
ChangeLog contents. It fails with an error that doesn't make
sense to me: the file it complains isn't mentioned clearly is
listed there and I can't tell what about how it's mentioned
the hook is
On 5/19/20 5:53 PM, Joseph Myers wrote:
On Tue, 19 May 2020, Martin Liška wrote:
On 5/19/20 10:11 AM, Martin Liška wrote:
Can you please share how do you do it? It would be easy to add it.
I added the feature via --fill-up-bug-titles option. It uses common
request and beatifulsoup packages.
On Tue, 2020-05-19 at 13:03 -0600, Martin Sebor via Gcc wrote:
> I'm having trouble with the commit hook that tries to enforce
> ChangeLog contents. It fails with an error that doesn't make
> sense to me: the file it complains isn't mentioned clearly is
> listed there and I can't tell what about h
On Tue, May 19, 2020 at 01:03:09PM -0600, Martin Sebor via Gcc wrote:
> I'm having trouble with the commit hook that tries to enforce
> ChangeLog contents. It fails with an error that doesn't make
> sense to me: the file it complains isn't mentioned clearly is
> listed there and I can't tell what
I'm having trouble with the commit hook that tries to enforce
ChangeLog contents. It fails with an error that doesn't make
sense to me: the file it complains isn't mentioned clearly is
listed there and I can't tell what about how it's mentioned
the hook is having a problem with.
Thanks
Martin
$
On Tue, 19 May 2020 at 17:36, Jonathan Wakely wrote:
>
> On Tue, 19 May 2020 at 17:19, Gerald Pfeifer wrote:
> >
> > I hope the offer by some of you to support people like me who Git
> > appears to hate with a fervor still stands? ;-)
> >
> > And I volunteer to enhance our documentation if it app
On Tue, 19 May 2020 at 17:19, Gerald Pfeifer wrote:
>
> I hope the offer by some of you to support people like me who Git
> appears to hate with a fervor still stands? ;-)
>
> And I volunteer to enhance our documentation if it appears useful.
>
>
> Usecase: I've got a patch approved and pushed to
On Tue, May 19, 2020 at 05:21:16PM +0100, Richard Earnshaw wrote:
> This is really a wart in the GNU coding style. And one reason why I
> tend to indent such labels by a single space. It particularly affects
> things like class definitions where public, private, etc statements
> often appear in c
On 19/05/2020 15:51, Michael Matz wrote:
> Hello,
>
> On Tue, 19 May 2020, Martin Liška wrote:
>
>>> The common problems I remember is that e.g. when changing a function comment
>>> above some function, it is attributed to the previous function rather than
>>> following, labels in function confus
On Mai 19 2020, Gerald Pfeifer wrote:
> What now?
$ sudo zypper in git-merge-changelog
$ git config --global merge.merge-changelog.name "GNU-style ChangeLog merge
driver"
$ git config --global merge.merge-changelog.driver "git-merge-changelog %O %A
%B"
$ printf "ChangeLog*\tmerge=merge-changelo
I hope the offer by some of you to support people like me who Git
appears to hate with a fervor still stands? ;-)
And I volunteer to enhance our documentation if it appears useful.
Usecase: I've got a patch approved and pushed to HEAD, and approved
for active release branches - 13a46321516e2efd
On Tue, 19 May 2020, Martin Liška wrote:
> On 5/19/20 10:11 AM, Martin Liška wrote:
> > Can you please share how do you do it? It would be easy to add it.
>
> I added the feature via --fill-up-bug-titles option. It uses common
> request and beatifulsoup packages.
The REST interface is much bette
Hello,
On Tue, 19 May 2020, Martin Liška wrote:
> > The common problems I remember is that e.g. when changing a function comment
> > above some function, it is attributed to the previous function rather than
> > following, labels in function confusing it:
> > void
> > foo ()
> > {
> > .
On 11/05/2020 17:43, Christophe Lyon via Gcc wrote:
> Hi,
>
>
> As you may know, I've been running validations of GCC trunk in many
> configurations for Arm and Aarch64.
>
>
> I was recently trying to make some cleanup in the new Bfloat16, MVE, CDE, and
> ACLE tests because in several configura
FYI: I've verified that when building with GCC 10, outline atomics are
correctly initialized on LSE machines. The ld.so ELF constructors
eventually get run and initialize __aarch64_have_lse_atomics.
One minor improvement would be to document __aarch64_have_lse_atomics as
interposable on the GCC s
On 5/19/20 10:53 AM, Martin Liška wrote:
On 5/19/20 10:11 AM, Martin Liška wrote:
Can you please share how do you do it? It would be easy to add it.
I added the feature via --fill-up-bug-titles option. It uses common
request and beatifulsoup packages.
Martin
Ok, I'm going to install the fol
Hello.
We've just installed server git hooks that verify git messages
for a correct ChangeLog format. For a limited time period, please
still apply ChangeLog changes to the corresponding ChangeLog files.
We'll use it for comparison of auto-generated CangeLog entries.
The format is documented her
On 5/19/20 10:23 AM, Jakub Jelinek wrote:
On Tue, May 19, 2020 at 10:11:28AM +0200, Martin Liška wrote:
I find this format more helpful for the reasons below so unless your
script can be tweaked to do something similar I'd like to be able to
continue to use mine going forward with the new infras
On 5/19/20 10:11 AM, Martin Liška wrote:
Can you please share how do you do it? It would be easy to add it.
I added the feature via --fill-up-bug-titles option. It uses common
request and beatifulsoup packages.
Martin
>From 5450c99b54131d1942ece3ffb6bbe415b1c85151 Mon Sep 17 00:00:00 2001
From
On Tue, May 19, 2020 at 10:11:28AM +0200, Martin Liška wrote:
> > I find this format more helpful for the reasons below so unless your
> > script can be tweaked to do something similar I'd like to be able to
> > continue to use mine going forward with the new infrastructure.
>
> Let's extend the c
On 5/15/20 5:06 PM, Martin Sebor wrote:
On 5/15/20 2:59 AM, Martin Liška wrote:
Hi.
Since we moved to git world and we're in the preparation for ChangeLog messages
being in git commit messages, I think it's the right time to also simplify mklog
script.
I'm sending a new version (which should e
32 matches
Mail list logo
