[PATCH 2/3] Enabled LRA for ia64.

gcc/ * config/ia64/ia64.cc: Enable LRA for ia64. * config/ia64/ia64.md: Likewise. * config/ia64/predicates.md: Likewise. --- gcc/config/ia64/ia64.cc | 7 ++- gcc/config/ia64/ia64.md | 4 ++-- gcc/config/ia64/predicates.md | 2 +- 3 files changed, 5

[PATCH 3/3] MAINTAINERS: Add myself as IA-64 maintainer.

MAINTAINERS | 1 + 1 file changed, 1 insertion(+) diff --git a/MAINTAINERS b/MAINTAINERS index e2870eef2ef..4328ca5f84c 100644 --- a/MAINTAINERS +++ b/MAINTAINERS @@ -78,6 +78,7 @@ i386 port Jan Hubicka i386 port Uros Bizjak i386 vector ISA

[PATCH 1/3] Remove ia64*-*-linux from the list of obsolete targets

The following un-deprecates ia64*-*-linux for GCC 15. Since we plan to support this for some years to come. gcc/ * config.gcc: Only exlicitly list ia64*-*-(hpux|vms|elf) in the list of obsoleted targets. contrib/ * config-list.mk (LIST): no --enable-obsolete for

[PATCH 0/3] Remove ia64*-*-linux from the list of obsolete targets

Hey there, I wanted to come back to maintaining the ia64 port as discussed preciously the other month on the gcc list. It has been some days as we were busy releasing the biggest release of our Embdded T2/Linux distribution [0] and we obviously did not want to propose to enable LRA for IA-64 in

[PATCH v2] fix PowerPC < 7 w/ Altivec not to default to power7

Hi Kewen, v2 with test case - I hope I worked all your nits in: Glibc uses .machine to determine assembler optimizations to use. However, since reworking the rs6000 .machine output selection in commit e154242724b084380e3221df7c08fcdbd8460674 22 May 2019, G5 as well as Cell, and even power4 w/

Re: [PATCH] fix PowerPC < 7 w/ Altivec not to default to power7

Hi Kewen, thank you for your reply. > on 2024/3/8 19:33, Rene Rebe wrote: > > This might not be the best timing -short before a major release-, > > however, Sam just commented on the bug I filled years ago [1], so here > > we go: > > > > Glibc uses .machine to

[PATCH] fix PowerPC < 7 w/ Altivec not to default to power7

This might not be the best timing -short before a major release-, however, Sam just commented on the bug I filled years ago [1], so here we go: Glibc uses .machine to determine assembler optimizations to use. However, since reworking the rs6000 .machine output selection in commit

[PATCH] fix PowerPC < 7 w/ Altivec not to default to power7

This might not be the best timing -short before a major release-, however, Sam just commented on the bug I filled years ago [1], so here we go: Glibc uses .machine to determine assembler optimizations to use. However, since reworking the rs6000 .machine output selection in commit

Re: GCC 4.1.2 RC1

Hi, On Tuesday 30 January 2007 04:06:36 Mark Mitchell wrote: GCC 4.1.2 RC1 is now on ftp://gcc.gnu.org and its mirrors. The canonical location is: ftp://gcc.gnu.org/pub/gcc/prerelease-4.1.2-20070128 As with all prereleases, the issue of most concern to me is packaging. Therefore, please

Re: Does SIMD optimization of GCC 3.4.6 work?

Hi, On Wednesday 05 July 2006 19:57, Mike Stump wrote: On Jul 4, 2006, at 7:43 PM, [EMAIL PROTECTED] wrote: The codec is at http://www.sourceforge.net/projects/openavs/. Currently, it requires a 3Ghz or better CPU to get a resonable framerate. I would like the codec to be useful even on

Re: Does SIMD optimization of GCC 3.4.6 work?

Hi, On Wednesday 05 July 2006 20:26, Dave Korn wrote: I believe Lionel's real problem is likely to be that he was hoping that turning on the -mmx -sse -sse2 -3dnow options would auto-vectorise his code for him. Lionel, (IIUIC) those options just /enable/ the use of the various SIMD

Re: How to use gcc4 to compile FreeBSD6.0 ?

On Thursday 29 June 2006 08:30, Beyond.Luo wrote: Hi, all When I compile FreeBSD6.0 using gcc4.1 instead of gcc3, lots of errors are reported. I knowes that gcc4.1 checks syntax more strictly, then how can I do now? any command-line options? Fix the code? -- René Rebe - Rubensstr. 64

GCC 4.1 and R_PPC64_ADDR32 out of range

Hi, not such an high priority, but testing the latest gcc 4.1.0 in whole system builds I stumble over: jackd: error while loading shared libraries: /usr/lib64/libjack.so.0: R_PPC64_ADDR32 4056b70 for symbol `' out of range There only R_PPC64_ADDR32 in .text+0*. Any idea or proposal how to

Re: GCC 4.1 and R_PPC64_ADDR32 out of range

Hi, On Tuesday 25 April 2006 14:21, Andrew Haley wrote: Rene Rebe writes: Hi, not such an high priority, but testing the latest gcc 4.1.0 in whole system builds I stumble over: jackd: error while loading shared libraries: /usr/lib64/libjack.so.0: R_PPC64_ADDR32 4056b70

Re: GCC 4.1 and R_PPC64_ADDR32 out of range

On Tuesday 25 April 2006 14:21, Andrew Haley wrote: Rene Rebe writes: Hi, not such an high priority, but testing the latest gcc 4.1.0 in whole system builds I stumble over: jackd: error while loading shared libraries: /usr/lib64/libjack.so.0: R_PPC64_ADDR32 4056b70

[BENCHMARK] comparing GCC 3.4 and 4.0 on an AMD Athlon-XP 2500+

Hi all, I have some preleminary benchmark results comparing 3.4(.3) with 4.0.0, including some optimization option permuations. http://exactcode.de/rene/hidden/gcc-article/2005-gcc-4.0/stat2-rt.png http://exactcode.de/rene/hidden/gcc-article/2005-gcc-4.0/stat2-bt.png rt = runtime bt =

gcc 4.0 miscompilation on sparc(32) with ultrasparc optmization

Hi all, this is just a tiny note, that gcc-4.0 does produce miscompiled binaries on sparc(32)-linux with -mcpu=ultrasparc. Some binaries work, however many such as bash, curl or gzip segfault. I know this is not a reduced testcase, just a note. I try to invest some time over the weekend to

Re: gcc 4.0 miscompilation on sparc(32) with ultrasparc optmization

Hi, Steven Bosscher wrote: this is just a tiny note, that gcc-4.0 does produce miscompiled binaries on sparc(32)-linux with -mcpu=ultrasparc. Some binaries work, however many such as bash, curl or gzip segfault. I know this is not a reduced testcase, just a note. I try to invest some time over