On Sat, 11 Jan 2020, Joseph Myers wrote:
> the older test conversions 1 through 7). Some cron jobs may be re-enabled
> before then, subject to testing (I have git changes to gcc_release ready,
> for example, for testing snapshot generation), but the DATESTAMP updates
> won't be enabled until t
Snapshot gcc-9-20200111 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/9-20200111/
and on various mirrors, see http://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 9 git branch
with the following options: git://gcc.gnu.org/git/gcc.git branch
Le 11/01/2020 à 14:49, Jakub Jelinek a écrit :
On Sat, Jan 11, 2020 at 07:43:17AM -0600, Segher Boessenkool wrote:
On Fri, Jan 10, 2020 at 07:50:02PM +0100, Jakub Jelinek wrote:
Maybe even add https://gcc.gnu.org/gNNN for 7-40 hexadecimal digits
redirect to https://gcc.gnu.org/git/gitweb.cg
On Sat, 11 Jan 2020, Thomas Koenig wrote:
> Hm... I just hope this is a one-time effect, and isn't an indication
> that git uses much more resources, server-side, so the current
> infrastructure is not up to the task. Is git that much more
> resource hungry than svn? Or is this unrelated?
I thin
Thomas Koenig :
> Hm... I just hope this is a one-time effect, and isn't an indication
> that git uses much more resources, server-side, so the current
> infrastructure is not up to the task. Is git that much more
> resource hungry than svn? Or is this unrelated?
Almost certanly unrelated. In nor
Hi Martin,
It does not for me
(something about public key rejected), but then I am a complete novice
at using git, so I am more or less doing vodoo git here.
Please paste the error message you face?
Currently, gcc.gnu.org is totally under water, even accessing the
wiki leads to a timeout, s
On Sat, 11 Jan 2020, Thomas Koenig wrote:
> Am 11.01.20 um 15:39 schrieb Joseph Myers:
> > This conversion is now in place, read-only for checking purposes. I've
> > done all the usual validation, including in particular checking branch
> > tips and tags against SVN.
>
> Is checkout via git+ssh
On 1/11/20 5:33 PM, Thomas Koenig wrote:
Am 11.01.20 um 15:39 schrieb Joseph Myers:
This conversion is now in place, read-only for checking purposes. I've
done all the usual validation, including in particular checking branch
tips and tags against SVN.
Is checkout via git+ssh supposed to work
On Jan 11 2020, Jakub Jelinek wrote:
> g:releases/gcc-9@{yesterday} references (and, there we at least shouldn't
@{yesterday} operates on reflogs, a local concept that is useless
outside your own repository.
Andreas.
--
Andreas Schwab, sch...@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5
On Jan 11 2020, Richard Earnshaw wrote:
> $ git ls-remote|grep vendors|sed -r "s|.*vendors/([^/]+).*|\1|"|sort|uniq
git ls-remote URL "*/vendors/*" | ...
Andreas.
--
Andreas Schwab, sch...@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1
"And now for some
On 11/01/2020 16:33, Thomas Koenig wrote:
> Am 11.01.20 um 15:39 schrieb Joseph Myers:
>> This conversion is now in place, read-only for checking purposes. I've
>> done all the usual validation, including in particular checking branch
>> tips and tags against SVN.
>
> Is checkout via git+ssh supp
On Jan 11 2020, Richard Earnshaw wrote:
> Once you have a checkout, "git ls-remote" will show all the refs on the
> server.
You don't need a checkout, git ls-remote works on a remote URL.
Andreas.
--
Andreas Schwab, sch...@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF7
Am 11.01.20 um 15:39 schrieb Joseph Myers:
This conversion is now in place, read-only for checking purposes. I've
done all the usual validation, including in particular checking branch
tips and tags against SVN.
Is checkout via git+ssh supposed to work for this? It does not for me
(something
On Sat, Jan 11, 2020 at 12:28:01PM +0100, Jakub Jelinek wrote:
> For the redirectors, it could be something like following patch, except the
> last new redirect would need also a yet to be written cgi script that would
> git undescr the argument and print
> Location: https://gcc.gnu.org/git/gitweb.
On Sat, 11 Jan 2020, Richard Earnshaw wrote:
> On 11/01/2020 14:58, Jakub Jelinek wrote:
> > On Sat, Jan 11, 2020 at 02:51:21PM +, Richard Earnshaw wrote:
> >> https://gcc.gnu.org/git/?p=gcc.git;a=shortlog;h=refs/vendors/redhat/heads/gcc-9-branch
> >>
> >> Works
> >>
> >> Or for tags s/heads/t
On 11/01/2020 15:01, Richard Earnshaw wrote:
> On 11/01/2020 14:58, Jakub Jelinek wrote:
>> On Sat, Jan 11, 2020 at 02:51:21PM +, Richard Earnshaw wrote:
>>> https://gcc.gnu.org/git/?p=gcc.git;a=shortlog;h=refs/vendors/redhat/heads/gcc-9-branch
>>>
>>> Works
>>>
>>> Or for tags s/heads/tags/
>>
On 11/01/2020 14:58, Jakub Jelinek wrote:
> On Sat, Jan 11, 2020 at 02:51:21PM +, Richard Earnshaw wrote:
>> https://gcc.gnu.org/git/?p=gcc.git;a=shortlog;h=refs/vendors/redhat/heads/gcc-9-branch
>>
>> Works
>>
>> Or for tags s/heads/tags/
>
> Indeed, this works, but if one doesn't know what b
On Sat, Jan 11, 2020 at 02:51:21PM +, Richard Earnshaw wrote:
> https://gcc.gnu.org/git/?p=gcc.git;a=shortlog;h=refs/vendors/redhat/heads/gcc-9-branch
>
> Works
>
> Or for tags s/heads/tags/
Indeed, this works, but if one doesn't know what branches there are for
particular vendor or what ven
On 11/01/2020 14:51, Richard Earnshaw wrote:
> On 11/01/2020 14:49, Richard Earnshaw wrote:
>> On 11/01/2020 14:48, Jakub Jelinek wrote:
>>> On Sat, Jan 11, 2020 at 02:39:43PM +, Joseph Myers wrote:
> On 11/01/2020 01:18, Joseph Myers wrote:
>> The GCC SVN repository is now read-only fo
On 11/01/2020 14:49, Richard Earnshaw wrote:
> On 11/01/2020 14:48, Jakub Jelinek wrote:
>> On Sat, Jan 11, 2020 at 02:39:43PM +, Joseph Myers wrote:
On 11/01/2020 01:18, Joseph Myers wrote:
> The GCC SVN repository is now read-only for the move to git, as is the
> old
> git-
On 11/01/2020 14:48, Jakub Jelinek wrote:
> On Sat, Jan 11, 2020 at 02:39:43PM +, Joseph Myers wrote:
>>> On 11/01/2020 01:18, Joseph Myers wrote:
The GCC SVN repository is now read-only for the move to git, as is the old
git-svn mirror; the cron job updating that mirror has been dis
On Sat, Jan 11, 2020 at 02:39:43PM +, Joseph Myers wrote:
> > On 11/01/2020 01:18, Joseph Myers wrote:
> > > The GCC SVN repository is now read-only for the move to git, as is the
> > > old
> > > git-svn mirror; the cron job updating that mirror has been disabled, as
> > > have gccadmin's cr
On Sat, 11 Jan 2020, Richard Earnshaw wrote:
> On 11/01/2020 01:18, Joseph Myers wrote:
> > The GCC SVN repository is now read-only for the move to git, as is the old
> > git-svn mirror; the cron job updating that mirror has been disabled, as
> > have gccadmin's cron jobs updating DATESTAMP, gen
On Sat, Jan 11, 2020 at 09:15:11AM -0500, Jason Merrill wrote:
> > On Fri, Jan 10, 2020 at 10:47:47PM +0100, Jakub Jelinek wrote:
> > > Ah, you suggested g: rather than just g.
> > > We could then support
> > > rN (1-6 decimal digits) - the svn revs, either for old repo, or
> > transformed
> >
On Sat, Jan 11, 2020 at 6:28 AM Jakub Jelinek wrote:
> On Fri, Jan 10, 2020 at 10:47:47PM +0100, Jakub Jelinek wrote:
> > Ah, you suggested g: rather than just g.
> > We could then support
> > rN (1-6 decimal digits) - the svn revs, either for old repo, or
> transformed
> > g:X (X is any
On Sat, Jan 11, 2020 at 07:43:17AM -0600, Segher Boessenkool wrote:
> On Fri, Jan 10, 2020 at 07:50:02PM +0100, Jakub Jelinek wrote:
> > Maybe even add https://gcc.gnu.org/gNNN for 7-40 hexadecimal digits
> > redirect to https://gcc.gnu.org/git/gitweb.cgi?p=gcc.git;h=NNN
> > and then just p
On Fri, Jan 10, 2020 at 07:50:02PM +0100, Jakub Jelinek wrote:
> Maybe even add https://gcc.gnu.org/gNNN for 7-40 hexadecimal digits
> redirect to https://gcc.gnu.org/git/gitweb.cgi?p=gcc.git;h=NNN
> and then just put as URL those
> https://gcc.gnu.org/g3b2b821c3f1bac2ac6dd2481f461ec33a13ea
On 11/01/2020 01:18, Joseph Myers wrote:
> The GCC SVN repository is now read-only for the move to git, as is the old
> git-svn mirror; the cron job updating that mirror has been disabled, as
> have gccadmin's cron jobs updating DATESTAMP, generating snapshots and
> updating online documentation
On 11/01/20 6:55 pm, Segher Boessenkool wrote:
> -ffreestanding means you might not have any of the C standard library,
> and -nostartfiles means you do not do any of the standard initialisation.
> Why then would you expect any ifunc to work?
>
Agreed, based on Alexander's feedback I have suggest
Hi!
On Fri, Jan 10, 2020 at 09:50:48PM +0530, Siddhesh Poyarekar wrote:
> Statically built independent programs that implement their own program
> entry points (i.e. -ffreestanding -nostartfiles) and call __builtin_*
> functions break when the builtin function in question is implemented as
> an IF
On Fri, Jan 10, 2020 at 12:38:10PM +0100, Richard Biener wrote:
> Just to chime in I also just want to get it done (well, I can handle
> SVN as well :P).
I will never have to learn it! I'm so happy!
> I trust Joseph, too, but then from my POV anything not worse than the current
> mirror works fo
On Fri, Jan 10, 2020 at 09:49:41AM +, Richard Earnshaw (lists) wrote:
> On 10/01/2020 07:33, Maxim Kuvyrkov wrote:
> >>On Jan 9, 2020, at 5:38 AM, Segher Boessenkool
> >> wrote:
> >>Where and when and by who was it decided to use this conversion?
> >
> >Joseph, please point to message on gcc@
On Thu, Jan 09, 2020 at 12:12:49PM +, Richard Earnshaw (lists) wrote:
> On 09/01/2020 02:38, Segher Boessenkool wrote:
> >Where and when and by who was it decided to use this conversion?
> >
> >Will it at least be *tested* first?
>
> Tested for what?
Acceptance test, of course, the only test
On Fri, Jan 10, 2020 at 10:47:47PM +0100, Jakub Jelinek wrote:
> Ah, you suggested g: rather than just g.
> We could then support
> rN (1-6 decimal digits) - the svn revs, either for old repo, or
> transformed
> g:X (X is any [0-9a-zA-Z_-], something else?, 1 or more chars) - gitweb
> wit
On Sat, Jan 11, 2020 at 2:02 AM Andrew Pinski wrote:
>
> Hi,
> I was looking into reassoc (for PR 93131) and I noticed that the
> alu.shift_reg is set to COSTS_N_INSNS (1). This prevents an
> optimization where we combine some if statements into shifts. I
> looked into the Corext A57 software
On Fri, Jan 10, 2020 at 07:50:02PM +0100, Jakub Jelinek wrote:
> The changes I was asking for is, for gcc master and releases/gcc-* branch
> commits to have the monotonically increasing short ids (printed by git descr
> with the git aliases I've posted) both somewhere early
> in the subject before
Hi,
I was looking into reassoc (for PR 93131) and I noticed that the
alu.shift_reg is set to COSTS_N_INSNS (1). This prevents an
optimization where we combine some if statements into shifts. I
looked into the Corext A57 software optimization guide[1] and saw that
shift with a register has a lat
37 matches
Mail list logo
