search for: o64

...hannel 0: input: no drain shortcut debug: channel 0: ibuf empty debug: channel 0: input drain -> wait_oclose debug: channel 0: send ieof debug: channel 0: write failed debug: channel 0: output open -> wait_ieof debug: channel 0: send oclose debug: channel 0: close_write debug: X11 closed 0 i4/o64 debug: channel 0: rcvd ieof debug: channel 0: non-open channel 0: istate 4 != open channel 0: ostate 64 != open debug: channel 0: rcvd oclose debug: channel 0: input wait_oclose -> closed X connection to pc07:10.0 broken (explicit kill or server shutdown). X forwarding is configured for both t...

The ELF relocation record format is different for N64 which many Mips 64 ABIs use than for O64 which many if not all other target ABIs use. The question I have is whether to treat N64 as a valid generic variant or should it be treated as target specific? My contention is that it should be treated as an alternative generic format handled recognized and handled in the ELF class objects above...

...the spec and given the popularity of GCC, the implementation became the new standard and it's something that LLVM needs to cope with. > There are a lot of MIPS ABIs. o32, n32, n64 - These came from the SGI world for IRIX originally, but were also adopted for linux and used in gcc for both. o64 - Invented at Cygnus for 64-bit processors eabi - Different one invented at Cygnus meabi - Invented with MIPS and Cygnus (and possibly others) in the late 90s as a new embedded abi. And there's been at least one or two other ABIs since - I'm pretty sure Imagination Technologies working up a...

Hi, I'd like to experiment with the MIPS and PowerPC backends, but, considering that they aren't widely used processors, I'd like to start with the same environment (OS/ABI/linker) used by the people who work with these backends. So, what OS/ABI/linker use the people who use these backends for production work? Thanks!!

...: input: no drain shortcut debug1: channel 0: ibuf empty debug1: channel 0: input drain -> wait_oclose debug1: channel 0: send ieof debug1: channel 0: write failed debug1: channel 0: output open -> wait_ieof debug1: channel 0: send oclose debug1: channel 0: close_write debug1: X11 closed 0 i4/o64 debug1: channel 0: rcvd oclose debug1: channel 0: input wait_oclose -> closed debug1: channel 0: rcvd ieof debug1: channel 0: non-open channel 0: istate 8 != open channel 0: ostate 64 != open XIO: fatal IO error 32 (Broken pipe) on X server "localhost:11.0" after 0 requests (0...

...ion rejected because of wrong authentication. debug: X11 rejected 0 i1/o16 debug: channel 0: INPUT_OPEN -> INPUT_WAIT_DRAIN [read failed] debug: channel 0: shutdown_read debug: channel 0: OUTPUT_OPEN -> OUTPUT_WAIT_IEOF [write failed] debug: channel 0: shutdown_write debug: X11 rejected 0 i2/o64 debug: channel 0: INPUT_WAIT_DRAIN -> INPUT_WAIT_OCLOSE [inbuf empty, send IEOF] debug: channel 0: OUTPUT_WAIT_IEOF -> OUTPUT_CLOSED [rvcd IEOF] debug: channel 0: INPUT_WAIT_OCLOSE -> INPUT_CLOSED [rcvd OCLOSE] debug: channel 0: full closed X connection to vaio.linnet.org:10.0 broken (expl...

...32bit > pointers > with 64 integers. This is what stock GCC targets by default for mips64. > LLVM for > mips64 targets N64 by default for historical reasons. > > Historically, MIPS has had other ABIs defined for it, such as GNU's EABI > and it's > 64 bit variant and O64. You can stick with O32/N64/N32 as most of the OS > distributions will only use those ABIs. > > The usual linker would be the GNU linker and GOLD. LLD is in a good shape > for > MIPS. > > For baremetal / embedded / kernel environments, the tools and ABIS are the > same but y...

...to cope with. >> >> > >> >> >> >> There are a lot of MIPS ABIs. >> >> >> >> o32, n32, n64 - These came from the SGI world for IRIX originally, >> >> but were also adopted for linux and used in gcc for both. >> >> o64 - Invented at Cygnus for 64-bit processors eabi - Different one >> >> invented at Cygnus meabi - Invented with MIPS and Cygnus (and >> >> possibly others) in the late 90s as a new embedded abi. >> >> And there's been at least one or two other ABIs since - I...

On 7/31/13 4:47 PM, Shuxin Yang wrote: > > On 7/31/13 4:30 PM, Tobias Grosser wrote: >> On 07/30/2013 09:44 PM, Chris Lattner wrote: >>> >>> On Jul 30, 2013, at 10:19 AM, Shuxin Yang <shuxin.llvm at gmail.com> >>> wrote: >>> >>>> The pro for running LICM early is that it may move big redundant >>>> stuff out of loop

...e new standard and it's something that >> LLVM needs to cope with. >> > >> >> There are a lot of MIPS ABIs. >> >> o32, n32, n64 - These came from the SGI world for IRIX originally, but were >> also adopted for linux and used in gcc for both. >> o64 - Invented at Cygnus for 64-bit processors eabi - Different one invented >> at Cygnus meabi - Invented with MIPS and Cygnus (and possibly others) in >> the late 90s as a new embedded abi. >> And there's been at least one or two other ABIs since - I'm pretty sure >> I...

...hannel 0: input: no drain shortcut debug: channel 0: ibuf empty debug: channel 0: input drain -> wait_oclose debug: channel 0: send ieof debug: channel 0: write failed debug: channel 0: output open -> wait_ieof debug: channel 0: send oclose debug: channel 0: close_write debug: X11 closed 0 i4/o64 debug: channel 0: rcvd ieof debug: channel 0: non-open channel 0: istate 4 != open channel 0: ostate 64 != open debug: channel 0: rcvd oclose debug: channel 0: input wait_oclose -> closed X connection to server:10.0 broken (explicit kill or server shutdown). userid at server[~:516] netstat -a |...

Thank you very much for your information and documents! Why Imagination Technologies do not offer the latest MIPS ABI document download link just like the ISA docs? If they thought no much people interested in that doc, they had to make greate effort on compiler like GCC,LLVM by themself,then why GCC disagree with some MIPS ABI, it should be freely designed by MIPS ABI designer and compiler

This to announce a test release of 2.1.0p1 before making it widely available. This release includes many fixes to problems reported over the last week. In particular: - spurious error and coredumps caused by the inbuilt entropy gathering - RSAref detection - Compilation fixes for Solaris and others It also contains (completely untested) support for compiling without RSA support. This may be

> > (from the context, you might have meant 'tuple' where you've written 'triple'. I'm answering based on the assumption you meant 'triple') > I did mean what I wrote. I thought I ought to check since it's very easy to mix up triples and tuples and the context sounded off. I'm glad I picked the right assumption. > > The proposed TargetTuple