RFA: [VAX] SUBREG of MEM with a mode dependent address

2014-05-25 Thread Matt Thomas
GCC 4.8 for VAX is generating a subreg:HI for mem:SI indexed address. This eventually gets caught by an assert in change_address_1. Since the MEM rtx is SI, legimate_address_p thinks it's fine. I have a change to vax.md which catches these but it's extremely ugly and I have to think there'

Re: RFA: [VAX] SUBREG of MEM with a mode dependent address

2014-06-03 Thread Matt Thomas
On May 30, 2014, at 10:39 AM, Jeff Law wrote: > On 05/25/14 18:19, Matt Thomas wrote: >> >> But even if movhi is a define_expand, as far as I can tell there's >> isn't enough info to know whether that is possible. At that time, >> how can I tell t

Re: GCC ARM: aligned access

2014-08-31 Thread Matt Thomas
On Aug 31, 2014, at 11:32 AM, Joel Sherrill wrote: >> Hi, >> >> I am writing some code and found that system crashed. I found it was >> unaligned access which causes `data abort` exception. I write a piece >> of code and objdump >> it. I am not sure this is right or not. >> >> command: >> arm-

Rogue SUBREG

2014-01-20 Thread Matt Thomas
I'm looking into http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58901 and trying to find where the following rtx is being generated: (subreg:HI (mem/u/c:SI (plus:SI (mult:SI (reg/v:SI 0 %r0 [orig:77 count ] [77]) (const_int 4 [0x4])) (symbol_ref:SI ("DECPOWERS") [flags 0x

Re: GCC 4.3 target deprecation proposals

2008-01-21 Thread Matt Thomas
ing is that NetBSD port to the vax is very much alive and maintained. Thus, I expect that those users (eg Matt Thomas) would like to see the GCC port retained. We would. I have gcc working with gcc4.3 but gcc's use mpfr/gmp has made native test impossible since neither work on vax/elf. I

[RFA] Invalid mmap(2) assumption in pch (ggc-common.c)

2005-04-23 Thread Matt Thomas
D set for architecture specific reasons). Is there a reason why MAP_FIXED isn't used even though it probably should be? -- Matt Thomas email: [EMAIL PROTECTED] 3am Software Foundry www: http://3am-software.com/bio/matt/ Cupertino, CA disclaimer:

[PATCH] VAX: cleanup; move macros from config/vax/vax.h to normal in config/vax/vax.c

2005-04-26 Thread Matt Thomas
Committed. -- Matt Thomas email: [EMAIL PROTECTED] 3am Software Foundry www: http://3am-software.com/bio/matt/ Cupertino, CA disclaimer: I avow all knowledge of this message. 2005-03-26 Matt Thomas <[EMAIL PROTECTED]> *

GCC 4.1: Buildable on GHz machines only?

2005-04-26 Thread Matt Thomas
just to see how much faster they are. I hope I'm going to pleasantly surprised but I'm not counting on it. -- Matt Thomas email: [EMAIL PROTECTED] 3am Software Foundry www: http://3am-software.com/bio/matt/ Cupertino, CA disclaimer: I avow all knowledge of this message.

Re: GCC 4.1: Buildable on GHz machines only?

2005-04-26 Thread Matt Thomas
only decreased the bootstrap time by 10%. By far, the longest bit of the bootstrap is building libjava. -- Matt Thomas email: [EMAIL PROTECTED] 3am Software Foundry www: http://3am-software.com/bio/matt/ Cupertino, CA disclaimer: I avow all knowledge of this message.

[RFA] Which is better? More and simplier patterns? Fewer patterns with more embedded code?

2005-04-26 Thread Matt Thomas
. For instance: (define_insn "*pushal" [(set (match_operand:SI 0 "push_operand" "=g") (match_operand:SI 0 "address_operand" "p"))] "" "pushal %a1") I like the more and simplier patterns approach

Re: GCC 4.1: Buildable on GHz machines only?

2005-04-26 Thread Matt Thomas
Gary Funck wrote: > >>-Original Message- >>From: Matt Thomas >>Sent: Tuesday, April 26, 2005 10:42 PM > > [...] > >>Alas, the --disable-checking and STAGE1_CFLAGS="-O2 -g" (which I was >>already doing) only decreased the bootstrap time

Re: GCC 4.1: Buildable on GHz machines only?

2005-04-27 Thread Matt Thomas
David Edelsohn wrote: >>>>>>Matt Thomas writes: > > > Matt> Regardless, GCC4.1 is a computational pig. > > If you are referring to the compiler itself, this has no basis in > reality. If you are referring to the entire compiler collection, > in

Re: GCC 4.1: Buildable on GHz machines only?

2005-04-27 Thread Matt Thomas
Jonathan Wakely wrote: > On Wed, Apr 27, 2005 at 08:05:39AM -0700, Matt Thomas wrote: > > >>David Edelsohn wrote: >> >> >>> GCC now supports C++, Fortran 90 and Java. Those languages have >>>extensive, complicated runtimes. The GCC Java envi

Re: GCC 4.1: Buildable on GHz machines only?

2005-04-27 Thread Matt Thomas
Mike Stump wrote: On Apr 26, 2005, at 11:12 PM, Matt Thomas wrote: It would be nice if bootstrap emitted timestamps when it was started and when it completed a stage so one could just look at the make output. You can get them differenced for free by using: time make boostrap I know that

Re: GCC 4.1: Buildable on GHz machines only?

2005-04-28 Thread Matt Thomas
he initial bootstrap compiler was gcc3.3 and they are all running off the same base of NetBSD 3.99.3. While taking out fortran and java reduced the disparity, there is still a large increase in bootstrap times from 3.4 to 4.1. -- Matt Thomas email: [EMAIL PROTECTED] 3am Softwa

Re: GCC 4.1: Buildable on GHz machines only?

2005-04-29 Thread Matt Thomas
table structure, the VAX uses a single page table of indirection. This greatly reduces the amount of address space a process can efficiently use. If there are components that will not be needed by some java programs, it would nice if they could be separated into their shared libraries.

VAX backend status

2007-04-01 Thread Matt Thomas
Over the past several weeks, I've revamped the VAX backend: - fixed various bugs - improved 64bit move, add, subtract code. - added patterns for ffs, bswap16, bswap32, sync_lock_test_and_set, and sync_lock_release - modified it to generate PIC code. - fixed the dwarf2 output so it is r

c-common.c line 5179: isn't this a nop?

2007-05-14 Thread Matt Thomas
In handle_aligned_attributes in c-common.c, at line 5146, it does type = &TREE_TYPE (decl); Then at 5179 it does TREE_TYPE (decl) = *type; In between, type doesn't change so that's really TREE_TYPE (decl) = * &TREE_TYPE (decl); or TREE_TYPE (decl) = TREE_TYPE

RFA: emitting .rodata before .text

2008-09-22 Thread Matt Thomas
In trying to make gcc for VAX pass test suites, one of the problems is gcc.c-torture/compile/pr34029-2.c in that the function foo is emitted before .rodata. This mean s & t are undefined and vax--netbsdelf-as doesn't like that. Moving .rodata before .text solves this but I can't see how to forc

Re: help for arm avr bfin cris frv h8300 m68k mcore mmix pdp11 rs6000 sh vax

2009-03-13 Thread Matt Thomas
On Mar 13, 2009, at 10:06 AM, Paolo Bonzini wrote: Hm. In fold-const.c we try to make sure to produce the same result as the target would for constant-folding shifts. Thus, Paolo, I think what fold-const.c does is what we should assume for !SHIFT_COUNT_TRUNCATED. No? Unfortunately it is

Re: %pc relative addressing of string literals/const data

2010-10-06 Thread Matt Thomas
On Oct 6, 2010, at 6:52 AM, Ian Lance Taylor wrote: > Joakim Tjernlund writes: > >> I really wish mrelocatable is added to all archs. The normal ELF relocs >> are too big to fit well in u-boot. > > Every architecture is different and requires a thoughtful approach to > determine the best way t

Re: constant string changed

2010-10-06 Thread Matt Thomas
On Oct 6, 2010, at 3:02 PM, Robert Dewar wrote: > On 10/6/2010 5:43 PM, Richard Guenther wrote: >> On Wed, Oct 6, 2010 at 11:34 PM, Phung Nguyen wrote: >>> How can I turn this optimization off? >> >> Use -fno-builtin-printf. > > I'm curious, it's obviously a correct optimization, so why > woul

Re: X32 psABI status

2011-02-12 Thread Matt Thomas
On Feb 12, 2011, at 1:29 PM, H.J. Lu wrote: > On Sat, Feb 12, 2011 at 1:10 PM, Florian Weimer wrote: >> * H. J. Lu: >> >>> We made lots of progresses on x32 pABI: >>> >>> https://sites.google.com/site/x32abi/ >>> >>> 1. Kernel interface with syscall is close to be finalized. >>> 2. GCC x32 br

Re: X32 psABI status

2011-02-12 Thread Matt Thomas
On Feb 12, 2011, at 7:02 PM, Andrew Pinski wrote: > On Sat, Feb 12, 2011 at 3:04 PM, H. Peter Anvin wrote: >> On 02/12/2011 01:10 PM, Florian Weimer wrote: >>> Why is the ia32 compatiblity kernel interface used? >> >> Because there is no way in hell we're designing in a second >> compatibility

Re: RFC: A new MIPS64 ABI

2011-02-14 Thread Matt Thomas
On Feb 14, 2011, at 12:29 PM, David Daney wrote: > Background: > > Current MIPS 32-bit ABIs (both o32 and n32) are restricted to 2GB of > user virtual memory space. This is due the way MIPS32 memory space is > segmented. Only the range from 0..2^31-1 is available. Pointer > values are always

Re: RFC: A new MIPS64 ABI

2011-02-14 Thread Matt Thomas
On Feb 14, 2011, at 6:22 PM, David Daney wrote: > On 02/14/2011 04:15 PM, Matt Thomas wrote: >> >> I have to wonder if it's worth the effort. The primary problem I see >> is that this new ABI requires a 64bit kernel since faults through the >> upper 2G will go

Re: RFC: A new MIPS64 ABI

2011-02-14 Thread Matt Thomas
On Feb 14, 2011, at 6:26 PM, David Daney wrote: > On 02/14/2011 06:14 PM, Joe Buck wrote: >> On Mon, Feb 14, 2011 at 05:57:13PM -0800, Paul Koning wrote: >>> It seems that this proposal would benefit programs that need more than 2 GB >>> but less than 4 GB, and for some reason really don't want

Re: RFC: A new MIPS64 ABI

2011-02-14 Thread Matt Thomas
On Feb 14, 2011, at 6:50 PM, David Daney wrote: > On 02/14/2011 06:33 PM, Matt Thomas wrote: >> >> On Feb 14, 2011, at 6:22 PM, David Daney wrote: >> >>> On 02/14/2011 04:15 PM, Matt Thomas wrote: >>>> >>>> I have to wonder if it'