Houssasam THH778, 4426 E Los Angeles Ave, Simi Valley, California 93063
Se désabonner
(https://hs-139700822.s.hubspotstarter-eu1.net/hs/manage-preferences/unsubscribe-all?languagePreference=fr&d=Vnb1QW7NVHjbVzpd8Q2m3_RVW1Jz9M11JDwVNVWwS3T3hSn4vVNw99V8Jzgb9N763PhLDnn3GW8J42G87CMRLCW5kTYZ11PRjpYV72
On Tue, 8 Sep 2020 at 17:33, Bruce Korb wrote:
>
> On Tue, Sep 8, 2020 at 7:36 AM Jakub Jelinek wrote:
> > > The fall through comment was polluted with a colon that I hadn't noticed,
> > > as in:
> > >
> > > /* FALLTHROUGH: */
> > >
> > > and your fall through regex doesn't allow for that.
>
On Tue, Sep 8, 2020 at 7:36 AM Jakub Jelinek wrote:
> > The fall through comment was polluted with a colon that I hadn't noticed,
> > as in:
> >
> > /* FALLTHROUGH: */
> >
> > and your fall through regex doesn't allow for that.
> > I'd add a colon to the space, tab and '!' that the regex acce
On Tue, Sep 08, 2020 at 07:28:45AM -0700, Bruce Korb via Gcc wrote:
> On Tue, Sep 8, 2020 at 2:33 AM Jonathan Wakely wrote:
> > > Nope. I had /* FALLTHROUGH */ on the line before a blank line before
> > > the case label. After Googling, I found an explicit reference that you
> > > had to spell it:
On Tue, Sep 8, 2020 at 2:33 AM Jonathan Wakely wrote:
> > Nope. I had /* FALLTHROUGH */ on the line before a blank line before
> > the case label. After Googling, I found an explicit reference that you
> > had to spell it: // fall through
> > I did that, and it worked. So I'm moving on, but still
On Mon, 7 Sep 2020 at 23:53, Bruce Korb via Gcc wrote:
>
> On Mon, Sep 7, 2020 at 3:45 PM Florian Weimer wrote:
> >
> > * Bruce Korb via Gcc:
> >
> > > I don't write a lot of code anymore, but this sure seems like a
> > > gratuitous irritation to me. I've been using
> > >
> > > // FALLTHRU an
On Mon, Sep 7, 2020 at 3:45 PM Florian Weimer wrote:
>
> * Bruce Korb via Gcc:
>
> > I don't write a lot of code anymore, but this sure seems like a
> > gratuitous irritation to me. I've been using
> >
> > // FALLTHRU and
> > // FALLTHROUGH
> >
> > for *DECADES*, so it's pretty incomprehen
* Bruce Korb via Gcc:
> I don't write a lot of code anymore, but this sure seems like a
> gratuitous irritation to me. I've been using
>
> // FALLTHRU and
> // FALLTHROUGH
>
> for *DECADES*, so it's pretty incomprehensible why the compiler should
> have to invalidate my code because it thi
I don't write a lot of code anymore, but this sure seems like a
gratuitous irritation to me. I've been using
// FALLTHRU and
// FALLTHROUGH
for *DECADES*, so it's pretty incomprehensible why the compiler should
have to invalidate my code because it thinks a different coding
comment is bet
Thanks both!
Cheers,
Tamar
> -Original Message-
> From: Martin Liška
> Sent: Wednesday, June 10, 2020 2:41 PM
> To: Tamar Christina ; Jonathan Wakely
>
> Cc: Jakub Jelinek ; gcc@gcc.gnu.org; gcc-patches patc...@gcc.gnu.org>
> Subject: Re: [IMPORTANT] ChangeLog
How do we handle multi author patches nowadays?
Tried searching for it on the website but couldn’t find anything.
Thanks,
Tamar
-Original Message-
From: Gcc-patches On Behalf Of Martin
Liška
Sent: Wednesday, June 10, 2020 8:38 AM
To: Jonathan Wakely
Cc: Jakub Jelinek ; gcc@gcc.g
On Wed, Jun 10, 2020 at 01:34:54PM +, Tamar Christina wrote:
> Hi All,
>
> We've been wondering since we no longer list authors in the changelog (at
> least mklog doesn't generate it),
> How do we handle multi author patches nowadays?
>
> Tried searching for it on the website but couldn’t fi
rom: Gcc-patches On Behalf Of Martin
> Liška
> Sent: Wednesday, June 10, 2020 8:38 AM
> To: Jonathan Wakely
> Cc: Jakub Jelinek ; gcc@gcc.gnu.org; gcc-patches patc...@gcc.gnu.org>
> Subject: Re: [IMPORTANT] ChangeLog related changes
>
> On 6/9/20 10:29 PM, Jonathan Wakely
On 6/9/20 10:29 PM, Jonathan Wakely wrote:
OK, here's a proper patch for the changes you liked, dropping the
changes to the Error exception type.
pytest contrib/gcc-changelog/test_email.py passes.
OK for master?
I like it and I've just pushed the patch to master.
Martin
On Tue, 2 Jun 2020 at 15:25, Martin Liška wrote:
>
> On 6/2/20 4:14 PM, Jonathan Wakely wrote:
> > On Tue, 2 Jun 2020 at 14:56, Jonathan Wakely wrote:
> >>
> >> On Tue, 2 Jun 2020 at 14:16, Martin Liška wrote:
> >>>
> >>> On 6/2/20 1:48 PM, Martin Liška wrote:
> I tend to this approach. Let
On 6/2/20 4:14 PM, Jonathan Wakely wrote:
On Tue, 2 Jun 2020 at 14:56, Jonathan Wakely wrote:
On Tue, 2 Jun 2020 at 14:16, Martin Liška wrote:
On 6/2/20 1:48 PM, Martin Liška wrote:
I tend to this approach. Let me prepare a patch candidate for it.
There's a patch for it. Can you please J
On Tue, 2 Jun 2020 at 14:56, Jonathan Wakely wrote:
>
> On Tue, 2 Jun 2020 at 14:16, Martin Liška wrote:
> >
> > On 6/2/20 1:48 PM, Martin Liška wrote:
> > > I tend to this approach. Let me prepare a patch candidate for it.
> >
> > There's a patch for it. Can you please Jonathan take a look?
>
>
On 6/2/20 3:56 PM, Jonathan Wakely wrote:
On Tue, 2 Jun 2020 at 14:16, Martin Liška wrote:
On 6/2/20 1:48 PM, Martin Liška wrote:
I tend to this approach. Let me prepare a patch candidate for it.
There's a patch for it. Can you please Jonathan take a look?
Looks great, thanks!
+
On Tue, 2 Jun 2020 at 14:16, Martin Liška wrote:
>
> On 6/2/20 1:48 PM, Martin Liška wrote:
> > I tend to this approach. Let me prepare a patch candidate for it.
>
> There's a patch for it. Can you please Jonathan take a look?
Looks great, thanks!
+if name not in wildcard_prefixe
On 6/2/20 1:48 PM, Martin Liška wrote:
I tend to this approach. Let me prepare a patch candidate for it.
There's a patch for it. Can you please Jonathan take a look?
Thanks,
Martin
>From 4d2cf31b6deb03c9ddc8062b9a45d2511e4a58bb Mon Sep 17 00:00:00 2001
From: Martin Liska
Date: Tue, 2 Jun 2020
On 6/2/20 1:22 PM, Jonathan Wakely via Gcc-patches wrote:
On Tue, 2 Jun 2020 at 12:09, Jonathan Wakely wrote:
On Tue, 2 Jun 2020 at 12:05, Jonathan Wakely wrote:
On Tue, 2 Jun 2020 at 11:56, Gerald Pfeifer wrote:
On Mon, 1 Jun 2020, Jonathan Wakely via Gcc-patches wrote:
The libstdc++ m
On Tue, 2 Jun 2020 at 12:09, Jonathan Wakely wrote:
>
> On Tue, 2 Jun 2020 at 12:05, Jonathan Wakely wrote:
> >
> > On Tue, 2 Jun 2020 at 11:56, Gerald Pfeifer wrote:
> > >
> > > On Mon, 1 Jun 2020, Jonathan Wakely via Gcc-patches wrote:
> > > > The libstdc++ manual is written in Docbook XML, bu
On Tue, 2 Jun 2020 at 12:05, Jonathan Wakely wrote:
>
> On Tue, 2 Jun 2020 at 11:56, Gerald Pfeifer wrote:
> >
> > On Mon, 1 Jun 2020, Jonathan Wakely via Gcc-patches wrote:
> > > The libstdc++ manual is written in Docbook XML, but we commit both the
> > > XML and generated HTML pages to Git. Som
On Tue, 2 Jun 2020 at 07:44, Martin Liška wrote:
>
> On 6/1/20 7:24 PM, Jonathan Wakely wrote:
> > On Mon, 25 May 2020 at 23:50, Jakub Jelinek via Gcc wrote:
> >>
> >> Hi!
> >>
> >> I've turned the strict mode of Martin Liška's hook changes,
> >> which means that from now on no commits to the tru
On Tue, 2 Jun 2020 at 11:56, Gerald Pfeifer wrote:
>
> On Mon, 1 Jun 2020, Jonathan Wakely via Gcc-patches wrote:
> > The libstdc++ manual is written in Docbook XML, but we commit both the
> > XML and generated HTML pages to Git. Sometimes a small XML file can
> > result in dozens of mechanical ch
On Mon, 1 Jun 2020, Jonathan Wakely via Gcc-patches wrote:
> The libstdc++ manual is written in Docbook XML, but we commit both the
> XML and generated HTML pages to Git. Sometimes a small XML file can
> result in dozens of mechanical changes to the generated HTML files,
> which we record in the Ch
On 6/1/20 7:24 PM, Jonathan Wakely wrote:
On Mon, 25 May 2020 at 23:50, Jakub Jelinek via Gcc wrote:
Hi!
I've turned the strict mode of Martin Liška's hook changes,
which means that from now on no commits to the trunk or release branches
should be changing any ChangeLog files together with th
On Mon, 25 May 2020 at 23:50, Jakub Jelinek via Gcc wrote:
>
> Hi!
>
> I've turned the strict mode of Martin Liška's hook changes,
> which means that from now on no commits to the trunk or release branches
> should be changing any ChangeLog files together with the other files,
> ChangeLog entry sh
On 5/31/20 10:27 PM, Segher Boessenkool wrote:
On Tue, May 26, 2020 at 03:14:02PM +0200, Andreas Schwab wrote:
On Mai 26 2020, Martin Liška wrote:
subprocess.check_output('git show --name-only --pretty="" | '
'grep ChangeLog | '
git show --name-only
On Tue, May 26, 2020 at 03:14:02PM +0200, Andreas Schwab wrote:
> On Mai 26 2020, Martin Liška wrote:
>
> > subprocess.check_output('git show --name-only --pretty="" | '
> > 'grep ChangeLog | '
>
> git show --name-only --pretty= -- '*ChangeLog*'
Or even ju
Hi Jakub,
On Tue, May 26, 2020 at 12:42:41PM +0200, Thomas Koenig wrote:
So, two questions:
- How do I get my gcc-10 branch back into a consistent state?
That works, thanks.
git reset --hard origin/releases/gcc-10
should do it (if you want to throw all your local changes).
- How are ba
On 5/26/20 3:14 PM, Andreas Schwab wrote:
-- '*ChangeLog*'
Thank you for the comment.
There's a proper patch for 'git gcc-backport' alias.
Thoughts?
Martin
>From a1511dd6ccda73befe3282c43671a6c4623d5d7d Mon Sep 17 00:00:00 2001
From: Martin Liska
Date: Tue, 26 May 2020 15:32:32 +0200
Subject
On Mai 26 2020, Martin Liška wrote:
> subprocess.check_output('git show --name-only --pretty="" | '
> 'grep ChangeLog | '
git show --name-only --pretty= -- '*ChangeLog*'
Andreas.
--
Andreas Schwab, sch...@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4
On 5/26/20 1:34 PM, Jakub Jelinek via Gcc wrote:
On Tue, May 26, 2020 at 12:27:59PM +0100, Richard Earnshaw wrote:
I haven't investigated in detail, but could we use a merge strategy with
the cherry-pick to drop ChangeLog entries?
If that works, sure.
Note, when cherry-picking commits from bef
On Tue, May 26, 2020 at 12:27:59PM +0100, Richard Earnshaw wrote:
> I haven't investigated in detail, but could we use a merge strategy with
> the cherry-pick to drop ChangeLog entries?
If that works, sure.
Note, when cherry-picking commits from before conversion to git or whenever
people started
On 26/05/2020 12:19, Jakub Jelinek via Gcc wrote:
> On Tue, May 26, 2020 at 12:42:41PM +0200, Thomas Koenig wrote:
>> Am 26.05.20 um 11:04 schrieb Thomas Koenig via Gcc:
>>> Am 26.05.20 um 00:48 schrieb Jakub Jelinek via Gcc:
>>>
I've turned the strict mode of Martin Liška's hook changes,
>>>
On Tue, May 26, 2020 at 12:42:41PM +0200, Thomas Koenig wrote:
> Am 26.05.20 um 11:04 schrieb Thomas Koenig via Gcc:
> > Am 26.05.20 um 00:48 schrieb Jakub Jelinek via Gcc:
> >
> > > I've turned the strict mode of Martin Liška's hook changes,
> >
> > This means that it is no longer possible to do
Am 26.05.20 um 11:04 schrieb Thomas Koenig via Gcc:
Am 26.05.20 um 00:48 schrieb Jakub Jelinek via Gcc:
I've turned the strict mode of Martin Liška's hook changes,
This means that it is no longer possible to do a git gcc-backport
[CC'ing fortran to warn other people against currently trying
Am 26.05.20 um 00:48 schrieb Jakub Jelinek via Gcc:
I've turned the strict mode of Martin Liška's hook changes,
This means that it is no longer possible to do a git gcc-backport
followed by a git push. If there is a procedure for this, it
is not documented on https://gcc.gnu.org/gitwrite.html
Great, thanks!
On Tue, May 26, 2020 at 2:08 PM Martin Liška wrote:
>
> On 5/26/20 7:22 AM, Hongtao Liu via Gcc wrote:
> > i commit a separate patch alone only for ChangeLog files, should i revert
> > it?
>
> Hello.
>
> I've just done it.
>
> Martin
--
BR,
Hongtao
On 5/26/20 7:22 AM, Hongtao Liu via Gcc wrote:
i commit a separate patch alone only for ChangeLog files, should i revert it?
Hello.
I've just done it.
Martin
On Tue, May 26, 2020 at 6:49 AM Jakub Jelinek via Gcc-patches
wrote:
>
> Hi!
>
> I've turned the strict mode of Martin Liška's hook changes,
> which means that from now on no commits to the trunk or release branches
> should be changing any ChangeLog files together with the other files,
> ChangeLo
Hi!
I've turned the strict mode of Martin Liška's hook changes,
which means that from now on no commits to the trunk or release branches
should be changing any ChangeLog files together with the other files,
ChangeLog entry should be solely in the commit message.
The DATESTAMP bumping script will b
Hello
We have a client who is interested in some of your services. I
will provide further details should we get a response from you.
Kind regards
Mr J. Hamilton
CEO
Hamtons Merchants Trading Co. Int'l
Hello,
Did you receive my previous email?
Pls inform.
Best regards,
T. K Acharya
Hello,
I have proposal for you please get back for details.
Suki Kaito
Hello,
I have proposal for you please get back for details.
Suki Kaito
On 04/14/2016 05:12 AM, Richard Biener wrote:
So it looks like we need to scrap one of the three GCC proposals
(currently all have Mentors "assigned" - well, not sure if
"want to mentor" counts as assigned).
There's the GIMPLE FE, Addressing mode selection and replacing
libiberty with gnulib.
Hi Richard,
Richard Biener writes:
> On Thu, 14 Apr 2016, Giuseppe Scrivano wrote:
>
>> Hi everyone,
>>
>> We got 18 slots from Google.
>>
>> It is less than we expected so not everyone is going to be satisfied by
>> the split below.
>>
>> We have time until next week (deadline April 20, 2016
On Thu, 14 Apr 2016, Giuseppe Scrivano wrote:
> Hi everyone,
>
> We got 18 slots from Google.
>
> It is less than we expected so not everyone is going to be satisfied by
> the split below.
>
> We have time until next week (deadline April 20, 2016 at 20:59 CEST)
> to assign mentors to each proje
I am forwarding it as I only saw it on the fortran@gcc but not on the
gcc@ list.
Original Message
Subject:IMPORTANT: sourceware.org hardware migration, MARCH 18..22
Date: Tue, 12 Mar 2013 11:36:04 -0400 (EDT)
From: Frank Ch. Eigler
Hi -
Please be aware that
undreds of thousands of files, convenience goes out the
window, and the important thing is instead, uniformity. The useful features are
the ones who behave in a simple way and always in the same way. That is the
only way, with such a large system, for a human to get a handle on the
behaviour of
member of FSF and did met me once to be able to
> put a face (mine) on MELT. Perhaps David Edelsohn or Diego Novillo or
> Ian Taylor [or even Sebastian Pop] are important people at the FSF. I
> really don't know (but I guess most of them are)! And I really don't
> understand th
On Sun, May 30, 2010 at 1:01 AM, Basile Starynkevitch
wrote:
>
> PS. The point is that from my far point of sight/view, understanding who
> is the "GCC Steering Comittee" [other that the few people speaking as SC
> at GCC Summit] and who is the "FSF" is very unclear.
http://gcc.gnu.org/steer
On Sun, 2010-05-30 at 02:10 +0200, Gerald Pfeifer wrote:
> On Sun, 30 May 2010, Basile Starynkevitch wrote:
> > Perhaps the question becomes: whom should I ask permission to add an
> > exception to MELT code's license to permit it to generate a *texi
> > documentation, or alternatively to relicense
On Sun, 30 May 2010, Basile Starynkevitch wrote:
> Perhaps the question becomes: whom should I ask permission to add an
> exception to MELT code's license to permit it to generate a *texi
> documentation, or alternatively to relicense all existing melt*texi
> files under GPL (so MELT documentation
king anyone at FSF?
The FSF is not in the business of giving free advice to anyone on
licensing issues. *if* you do something that violates the license,
and *if* it is deemed important enough to do something about, then
the FSF *may* take some action.
transition was made to GPLv3. Not a big deal in practice.
>
> > What I am very scared of, is to make someone at FSF unhappy or angry
> > against me.
>
> sorry to be this blunt but if you are not engaging in questionable activity
> with
> GCC, you are not"importa
lking about legal issues in substance.
[...]
> What I am very scared of, is to make someone at FSF unhappy or angry
> against me.
sorry to be this blunt but if you are not engaging in questionable activity with
GCC, you are not"important" enough to get people at FSF mad at you :-)
on a
different continent, I am not a native English speaker, etc..]. I don't
know who is an influent member of FSF and did met me once to be able to
put a face (mine) on MELT. Perhaps David Edelsohn or Diego Novillo or
Ian Taylor [or even Sebastian Pop] are important people at the FSF.
Basile Starynkevitch wrote:
Does any one know any name of a person from FSF who could give a
practical advice? I know nobody in person from FSF - unless there have
been some FSF people at some GCC summit I did attend.
You really can't expect to get free legal advice from the FSF. If
you need l
On Sat, 2010-05-29 at 15:49 +0200, Steven Bosscher wrote:
>
> Yes. Read your copyright assignment. You have perpetual rights to do
> as you see fit with the code you wrote, even if you assigned copyright
> to the FSF.
Perhaps this might solve my GPL vs GFDL issues on the MELT branch (where
a *te
lördag 29 maj 2010 15.45.09 skrev Marc Espie:
> So, I used to contribute back to gcc regularly, got overwhelmed by
> other stuff, but I'm back.
>
> Case in point: I've added stuff to OpenBSD for secure handling of
> trampolines. Since trampolines require an executable stack, we want to
> make s
On Sat, May 29, 2010 at 03:49:48PM +0200, Steven Bosscher wrote:
> On Sat, May 29, 2010 at 3:45 PM, Marc Espie wrote:
>
> > Is there something I'm missing ? Is there a way I can still be the owner
> > of that patch and release it as I wish ?
>
> Yes. Read your copyright assignment. You have per
On Sat, 2010-05-29 at 15:45 +0200, Marc Espie wrote:
>
> However, if I submit it, per-the-rules, against gcc-current, for it to be
> integrated, I need to waive my rights (I have a (c) assignment already on
> record at the FSF, so a priori, I don't need more paperwork).
>
> If I recall correctly,
> If I recall correctly, it means I transfer all possible rights to the FSF.
> I no longer own my patch.
>
> Then it gets released as part of gcc-current, under the GPLv3.
>
> If I get things correctly *I can no longer release it under GPLv2+*, as we
> do for our mutant fork of gcc 4.2.1.
>
> Is
On Sat, May 29, 2010 at 3:45 PM, Marc Espie wrote:
> Is there something I'm missing ? Is there a way I can still be the owner
> of that patch and release it as I wish ?
Yes. Read your copyright assignment. You have perpetual rights to do
as you see fit with the code you wrote, even if you assig
So, I used to contribute back to gcc regularly, got overwhelmed by
other stuff, but I'm back.
Case in point: I've added stuff to OpenBSD for secure handling of trampolines.
Since trampolines require an executable stack, we want to make sure we don't
have trampolines all over the place, hence a -ft
Salut !
Royal Contact a maintenant décidé d'orienter sa clientèle dans la tranche d'âge
entre 18 et 40 ans.
Une publicité sera faite dans les CEGEPS et Universités pour recrutter du
nouveau monde.
Si vous êtes dans cette tranche d'âge, Faites-vous une fiche sur le site et une
fois entré, cliq
On Apr 12, 2005, at 12:59 PM, Karel Gardas wrote:
Either cachegrind is wrong, or gcc gets much better from that time?
Or do
I interpret cachegrind provided data in the wrong way? What do you
think
about it?
Or you're comparing x86 to power, and noticing that the x86 has to
execute way more da
On Tue, 12 Apr 2005, Karel Gardas wrote:
cachegrind can also be used to estimate the number (though, not sure
how accurate it is, possibly not very). I use Shark to actually get
the real number.
Perhaps it's possible that cachegrind is wrong or cache misses differ from
platform to platform, but I
On Tue, 12 Apr 2005, Mike Stump wrote:
> On Tuesday, April 12, 2005, at 06:38 AM, Karel Gardas wrote:
> > Especially: ``Currently gcc takes a cache miss every 20 instructions,
> > or
> > some ungodly number, and that really saps performance.''
> >
> > but I don't know if this is just an 1st April
On Tuesday, April 12, 2005, at 06:38 AM, Karel Gardas wrote:
Especially: ``Currently gcc takes a cache miss every 20 instructions,
or
some ungodly number, and that really saps performance.''
but I don't know if this is just an 1st April fool joke
Nope, no joke. The exact number will vary from m
On Tue, 12 Apr 2005, Karel Gardas wrote:
> using cache and how much cache it needs (I'm cosidering 512KB cache CPU
> here either Winchester or Venice core) and that's the reason why I ask
> here, since I've not been able so far to search by google for sufficient
> answer for this question.
Also t
Hello,
first of all, I'm sorry for off-topic, the question from subject might
look silly to you, since natural answer might be "it is very important",
but in the light of deciding what and how much memory will I need in AMD64
box, I've got into deciding troubles caused by the
76 matches
Mail list logo
