On Thu, Jan 2, 2020 at 4:00 AM Jerry wrote:
>
> In the following git log entry, I made a typo on the PR number in the
> libgfortran ChangeLog file. I noticed this right after the git commit,
> while editing the git log.
>
> So I quit the edit without saving and git reported that the commit was
> a
On 02/01/2020 02:00, Jerry wrote:
> In the following git log entry, I made a typo on the PR number in the
> libgfortran ChangeLog file. I noticed this right after the git commit,
> while editing the git log.
>
> So I quit the edit without saving and git reported that the commit was
> aborted.
>
>
On 02/01/2020 02:58, Alexandre Oliva wrote:
> On Dec 30, 2019, "Richard Earnshaw (lists)" wrote:
>
>> Right, (and wrong). You have to understand how the release branches and
>> tags are represented in CVS to understand why the SVN conversion is done
>> this way.
>
> I'm curious and ignorant, is
On 1/2/20 11:49 AM, Richard Earnshaw wrote:
On 02/01/2020 02:00, Jerry wrote:
In the following git log entry, I made a typo on the PR number in the
libgfortran ChangeLog file. I noticed this right after the git commit,
while editing the git log.
...
If you've pushed the branch to a public
On 1/1/20 4:31 AM, The Other wrote:
Hi,
I'm currently working on a Rust frontend for GCC. Rust has some
language-level conditional compilation features based on the presence or
lack of features in the target architecture (e.g. SSE, AVX, a static C
runtime) as well as the target CPU architecture i
On Thu, 2 Jan 2020 at 02:00, Jerry wrote:
>
> In the following git log entry, I made a typo on the PR number in the
> libgfortran ChangeLog file. I noticed this right after the git commit,
> while editing the git log.
>
> So I quit the edit without saving and git reported that the commit was
> abo
One of the engineers here at Marvel was experimenting, at the user level, with
GCC in a failed attempt
to get loop blocking to do loop blocking. Here's basically his question.
Exactly how does loop blocking work in GCC?
I know this must involve the polyhedral optimization code so an explanatio
On January 3, 2020 2:04:20 AM GMT+01:00, Gary Oblock
wrote:
>One of the engineers here at Marvel was experimenting, at the user
>level, with GCC in a failed attempt
>to get loop blocking to do loop blocking. Here's basically his
>question.
>
> Exactly how does loop blocking work in GCC?
>
>I kno
