ected problems related to your patch(es). Please find
some details below.
In gcc_check master-arm, after:
| gcc patch https://patchwork.sourceware.org/patch/105574
| Author: Siddhesh Poyarekar
| Date: Tue Jan 28 12:43:50 2025 -0500
|
| [PATCH v3] testsuite/118127: Pass fortran
-tcwg channel, or ping your favourite Linaro toolchain developer on the
usual project channel.
In CI config tcwg_glibc_check/master-arm after:
| glibc patch https://patchwork.sourceware.org/patch/75959
| Author: Siddhesh Poyarekar
| Date: Thu Sep 14 06:13:02 2023 -0400
|
| getadd
Hello folks,
I got a few people asking me to do this in the last Connect, so I've
proposed a beginner session that explores gcc under the hood. The
tentative plan I have for the talk is:
1. A high level view of how the source code is laid out
2. Front end, middle end, backend. This includes a h
On Mon, 18 Jun 2018 at 14:54, Ramana Radhakrishnan
wrote:
> I don't think the make bench discussion is totally relevant in this
> case. We'd like to see what the performance of this stuff is and it's
> always goign to be a battle to get things benchmarked perfectly on
> hardware and there is unli
On 31 May 2018 at 23:07, Richard Henderson wrote:
> Thanks. I believe I've now successfully done so.
> Please let me know if my procedure is off; this is
> my first time using gerrit.
You need to add reviewers to your review requests. I'd suggest adding
at least Adhemerval, Christophe and Maxim
On 31 May 2018 at 09:38, Richard Henderson wrote:
> I spoke with Ramana about these at HKG18, and I'm finally getting back to
> these. I have routines for
>
> -rw-rw-r--. 1 rth rth 2538 May 30 19:12 memchr.S
> -rw-rw-r--. 1 rth rth 2405 May 30 20:49 memcmp.S
> -rw-rw-r--. 1 rth rth 2385 May 30 19
On 19 January 2016 at 18:04, Adhemerval Zanella
wrote:
> I do see some x86_64 specialized implementation being used currently
> (sysdeps/x86_64/fpu/s_{sin,cos}f.S for instance). The sincos implementations
> is still used (sysdeps/x86_64/fpu/s_sincosf.S).
>
> What you referring that glibc has dropp
On 19 January 2016 at 00:06, Adhemerval Zanella
wrote:
> No one has posted any patch or stirred discussions about it. The complex
> function in libm are usually coded in in C to be platform neutral, with
> some specific function being optimized (rounding, etc.). x86_64 also have
> some assembly i
