Re: Resend: Potential upcoming changes in mangling to PowerPC GCC

Segher Boessenkool writes: > You can write > double convert (__ibm128 x) { return x; } > double convert (__ieee128 x) { return x; } > as well. "__ieee128" and "long double" are the same type then (and the > same as _Float128 and __float128 as well). Oh! I see. Thanks! Going back

Re: Resend: Potential upcoming changes in mangling to PowerPC GCC

Michael Meissner via Gcc writes: > Because long double mangles the same as either __float128 or __ibm128, you > cannot write programs like: > > double convert (__ibm128x) { return x; } > double convert (__float128 x) { return x; } > double convert (long double x) { return

Re: [PATCH v2] powerpc: add documentation for HWCAPs

Segher Boessenkool writes: > That is a usability problem. Can it be fixed, or will that create its > own compatibility problems? In practice I mean. If it is, the C > libraries could fix it up, for new programs, and then after a while the > kernel can do the sane thing? > > How big is the

Re: [PATCH v2] powerpc: add documentation for HWCAPs

Nicholas Piggin writes: > +PPC_FEATURE_ARCH_2_05 > +The processor supports the v2.05 userlevel architecture. Processors > +supporting later architectures also set this feature. I don't think this bit is enabled when processors support later architectures. In my tests, this behavior

Re: [POWER10] __morestack calls from pcrel code

Alan Modra via Gcc-patches writes: > Compiling gcc/testsuite/gcc.dg/split-*.c and others with -mcpu=power10 > and linking with a non-pcrel libgcc results in crashes due to the > power10 pcrel code not having r2 set for the generic-morestack.c > functions called from __morestack. There is also a

Re: [PATCH] libstdc++: Add C++ runtime support for new 128-bit long double format

Jonathan Wakely writes: >>Hmm, yes, you pointed me to __frexpieee128 a few months ago, but for >>some reason I either didn't switch to using it, or lost a patch when >>squashing and rebasing branches. Hopefully I just forgot to change it, >>but I'll double check to make sure I haven't left any

Re: [PATCH] libstdc++: Add C++ runtime support for new 128-bit long double format

Jonathan Wakely via Libstdc++ writes: > diff --git a/libstdc++-v3/configure.ac b/libstdc++-v3/configure.ac > index cbfdf4c6bad..d25842fef35 100644 > --- a/libstdc++-v3/configure.ac > +++ b/libstdc++-v3/configure.ac > @@ -421,12 +425,43 @@ case "$target" in > >

Re: [PATCH] rs6000: Fix extraneous characters in the documentation

Ping? Tulio Magno Quites Machado Filho via Gcc-patches writes: > Replace them with a whitespace in order to avoid artifacts in the HTML > document. > > 2020-08-19 Tulio Magno Quites Machado Filho > > gcc/ > * doc/extend.texi (PowerPC Built-in Functions): Repla

[PATCH] rs6000: Fix extraneous characters in the documentation

Replace them with a whitespace in order to avoid artifacts in the HTML document. 2020-08-19 Tulio Magno Quites Machado Filho gcc/ * doc/extend.texi (PowerPC Built-in Functions): Replace extraneous characters with whitespace. --- gcc/doc/extend.texi | 6 +++--- 1 file changed

Re: GLIBC libmvec status

Bill Schmidt writes: > One tiny nit on the document: For the "b" value, let's just say "VSX" > rather than > "VSX as defined in PowerISA v2.07)." We will plan to only change > values in case > a different vector length is defined in future. That change would have more implications: all

Re: GLIBC libmvec status

Jakub Jelinek writes: > Can you please explain how do you want to pass the > void sincos (double, double *, double *); > arguments? I must say it isn't entirely clear from the document. > You talk there about double[2], but sincos certainly doesn't have such an > argument. The plan [1] is to

Re: GLIBC libmvec status

GT writes: > Are we all agreed that the POWER Vector Function ABI will be implemented only > for powerpc64le? > > If so, here are a few more questions: > > 1. The GLIBC implementation has files Makefile, Versions, configure, > configure.ac among others > in directory

Re: [RFC PATCH v0] PPC64: Implement POWER Architecure Vector Function ABI.

Jakub Jelinek writes: > On Sun, Feb 23, 2020 at 10:55:53AM -0600, Bill Schmidt wrote: >> > If/when it becomes necessary to have 'c' variants of functions, then a new >> > version of >> > the Vector Function ABI document will be created. And GLIBC and GCC >> > modifications to >> > comply with

Re: RFC: Extending --with-advance-toolchain to aarch64

Steve Ellcey writes: > I have a question about building a toolchain that uses (at run time) a > dynamic linker and system libraries and headers that are in a non-standard > place. > > I just noticed the IBM --with-advance-toolchain option and I would > like to replicate it for aarch64. > > Let

[PATCHv2] Change the library search path when using --with-advance-toolchain

64 so that user directories specified at build time have higher preference over the advance toolchain libraries. Set MD_STARTFILE_PREFIX to $prefix/lib/ and MD_STARTFILE_PREFIX_1 to $at/lib/ so that a compiler library has preference over the Advance Toolchain libraries. 2019-10-04 Tulio Magno

[PATCH] Remove extra lib directory from --with-advance-toolchain

Remove the extra -L directory so that user directories specified at build time have higher preference over the advance toolchain libraries. 2019-10-03 Tulio Magno Quites Machado Filho * config.gcc: Remove an extra -L from --with-advance-toolchain. --- gcc/config.gcc | 6 ++ 1

[PATCH] powerpc: Fix typos in the manual

[gcc] 2018-10-26 Tulio Magno Quites Machado Filho * doc/extend.texi (PowerPC builtins): Fix __builtin_unpack_ibm128 return type and other typos. --- gcc/doc/extend.texi | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/gcc/doc/extend.texi b/gcc/doc

Re: [PATCH], Add configuration checks to PowerPC --with-long-double-format=ieee

Michael Meissner writes: > On Fri, Jul 06, 2018 at 10:16:34AM -0300, Tulio Magno Quites Machado Filho > wrote: >> I suggest to test with the following program: >> >> #include >> >> int >> main () >> { >> return !isinfl(__bu

Re: [PATCH], Add configuration checks to PowerPC --with-long-double-format=ieee

Michael Meissner writes: > This patch adds a simple check of whether the GLIBC should be capable of > switching the long double format on the PowerPC to IEEE 128-bit floating > point. > At the moment, library work is not yet finished, but I'm assuming that the > patches will be in place when

Re: [PATCHv2] PR libstdc++/84654 Do not use __float128 if it is disabled by the compiler

Ping? Tulio Magno Quites Machado Filho <tul...@linux.vnet.ibm.com> writes: > Changes since v1: > - Completely rewrite of the patch to set ENABLE_FLOAT128 at libstdc++ >build time and undef _GLIBCXX_USE_FLOAT128 when building user code. > > --- 8< --- > > I

[PATCHv2] PR libstdc++/84654 Do not use __float128 if it is disabled by the compiler

ode. This patch changes the behavior at libstdc++ build by setting ENABLE_FLOAT128, which is used to set the value of the exported macro _GLIBCXX_USE_FLOAT128. 2018-03-12 Tulio Magno Quites Machado Filho <tul...@linux.vnet.ibm.com> PR libstdc++/84654 * acinclude.m4: Set ENABLE

[PATCH] PR libstdc++/84654 Do not use __float128 if it is disabled by the compiler

In order to use the __float128 in C++ it's necessary to check if it is supported in libstdc++ (i.e. via _GLIBCXX_USE_FLOAT128) and if the compiler enabled its support too, e.g. -mfloat128 or -mno-float128. 2018-03-01 Tulio Magno Quites Machado Filho <tul...@linux.vnet.ibm.com> PR l

Re: [PATCH, rs6000] Add support to __builtin_cpu_supports() for new HWCAP2 bit

Peter Bergner writes: > On 11/6/17 4:52 PM, Segher Boessenkool wrote: >> Hi! >> >> On Mon, Nov 06, 2017 at 11:41:39AM -0600, Peter Bergner wrote: >>> There is a new HWCAP2 bit added to the AUXV here: >>> >>> http://patchwork.ozlabs.org/patch/824764/ >>> >>> This patch

Re: [PATCH, rs6000] Add support to __builtin_cpu_supports() for two new HWCAP2 bits

Segher Boessenkool writes: > On Fri, Jun 30, 2017 at 11:53:48AM -0500, Peter Bergner wrote: >> >> Not use an installed header, that's not what I'm asking. Share the >> >> source file, i.e., just copy it over from the glibc source tree (it >> >> should probably hold

Re: [PATCH] builtin expansion of strncmp for rs6000

Segher Boessenkool writes: > On Thu, Jan 12, 2017 at 05:53:06PM +, Joseph Myers wrote: >> On Thu, 15 Dec 2016, Aaron Sawdey wrote: >> >> > + emit_library_call_value (gen_rtx_SYMBOL_REF (Pmode, "strncmp"), >> > + target, LCT_NORMAL,

[PATCH] Enable support for init/fini_array on cross compilers if glibc = 2.4

Support for .preinit_array/.init_array/.fini_array has been available in glibc since version 2.4. [gcc] 2014-08-27 Tulio Magno Quites Machado Filho tul...@linux.vnet.ibm.com * acinclude.m4: Automatically detect if glibc supports .preinit_array/.init_array/.fini_array on cross

[PATCHv4] rs6000: Add 2 built-ins to read the Time Base Register on PowerPC

significant word on 32-bit environments and the whole Time Base value on 64-bit. [gcc] 2012-09-17 Tulio Magno Quites Machado Filho tul...@linux.vnet.ibm.com * config/rs6000/rs6000-builtin.def: Add __builtin_ppc_get_timebase and __builtin_ppc_mftb. * config/rs6000/rs6000.c

[PATCHv5] rs6000: Add 2 built-ins to read the Time Base Register on PowerPC

the least significant word on 32-bit environments and the whole Time Base value on 64-bit. [gcc] 2012-09-19 Tulio Magno Quites Machado Filho tul...@linux.vnet.ibm.com * config/rs6000/rs6000-builtin.def: Add __builtin_ppc_get_timebase and __builtin_ppc_mftb. * config/rs6000/rs6000

[PATCHv3] rs6000: Add 2 built-ins to read the Time Base Register on PowerPC

__builtin_ppc_mftb generates only 1 instruction and returns the least significant word on 32-bit environments and the whole Time Base value on 64-bit. [gcc] 2012-09-17 Tulio Magno Quites Machado Filho tul...@linux.vnet.ibm.com * config/rs6000/rs6000-builtin.def: Add

[PATCH v2] rs6000: Add 2 built-ins to read the Time Base Register on PowerPC

__builtin_ppc_mftb generates only 1 instruction and returns the least significant word on 32-bit environments and the whole Time Base value on 64-bit. [gcc] 2012-09-14 Tulio Magno Quites Machado Filho tul...@linux.vnet.ibm.com * config/rs6000/rs6000-builtin.def: Add

Re: [PATCH v2] rs6000: Add 2 built-ins to read the Time Base Register on PowerPC

Segher Boessenkool seg...@kernel.crashing.org writes: Hi Tulio, Hi Segher, +(define_expand rs6000_get_timebase + [(use (match_operand:DI 0 gpc_reg_operand ))] + + +{ + if (TARGET_POWERPC64) +emit_insn (gen_rs6000_get_timebase_ppc64 (operands[0])); + else +emit_insn

Re: [PATCH v2] rs6000: Add 2 built-ins to read the Time Base Register on PowerPC

Segher Boessenkool seg...@kernel.crashing.org writes: I don't think TARGET_MFCRF is correct. For example, if you use -mcpu=powerpc64 (which doesn't set this flag) you will get code that does not run on the newer machines. Sorry, but it seems to be working here... I explain how I tested

[PATCH] rs6000: Add a builtin to read the time base register on PowerPC

Add __builtin_ppc_get_timebase to read the time base register on PowerPC. This is required for applications that measure time at high frequencies with high precision that can't afford a syscall. [gcc] 2012-08-29 Tulio Magno Quites Machado Filho tul...@linux.vnet.ibm.com * config/rs6000

Re: [PATCH] rs6000: Add a builtin to read the time base register on PowerPC

Hi Segher, Segher Boessenkool seg...@kernel.crashing.org writes: Add __builtin_ppc_get_timebase to read the time base register on PowerPC. This is required for applications that measure time at high frequencies with high precision that can't afford a syscall. For things that do mftb with

Re: [PATCH] rs6000: Add a builtin to read the time base register on PowerPC

Segher Boessenkool seg...@kernel.crashing.org writes: For things that do mftb with high frequency, maybe you should also add a builtin that does just an mftb, i.e. returns a 32-bit result on 32- bit implementations. Are you thinking in a function that returns only the TBL? On 32-bit,