Displaying 20 results from an estimated 20000 matches similar to: "[LLVMdev] test-suite failures"
2011 Nov 07
0
[LLVMdev] test-suite failures
Reed,
On Nov 7, 2011, at 2:11 PM, reed kotler wrote:
> We have a modified version of projects/test-suite that we can run cross
> using Qemu.
>
> We would like to put that back so that other people can test MIPS
> before putting back.
> Well, this would be easily modifiable for ARM and other targets that are
> supported by QEMU.
>
> But in this case, we would need
2011 Nov 08
1
[LLVMdev] test-suite failures
On 11/07/2011 02:29 PM, Eli Friedman wrote:
> On Mon, Nov 7, 2011 at 2:11 PM, reed kotler<rkotler at mips.com> wrote:
>> We have a modified version of projects/test-suite that we can run cross
>> using Qemu.
>>
>> We would like to put that back so that other people can test MIPS
>> before putting back.
>> Well, this would be easily modifiable for ARM
2011 Nov 07
0
[LLVMdev] test-suite failures
On Mon, Nov 7, 2011 at 2:11 PM, reed kotler <rkotler at mips.com> wrote:
> We have a modified version of projects/test-suite that we can run cross
> using Qemu.
>
> We would like to put that back so that other people can test MIPS
> before putting back.
> Well, this would be easily modifiable for ARM and other targets that are
> supported by QEMU.
>
> But in this
2013 Jun 07
2
[LLVMdev] tools build issue with lnt in cross platform testing
I want to get lnt to use qemu for the execution.
In that case, RHOST= is not set.
But I change the Arch because I am going to run in cross mode.
Then I'm setting RUNUNDER to be a script which runs qemu.
In this case it builds timeit-target as a Mips which fails because this
is running on x86.
~/mysandbox/bin/lnt runtest nt --sandbox ~/mysandbox --cc
/local/llvmpb_a/install/bin/clang
2013 Jun 07
0
[LLVMdev] tools build issue with lnt in cross platform testing
The issues seems to be this line in the tools Makefile
timeit-target: timeit.c
$(LD_ENV_OVERRIDES) $(LCC) -o $@ $< $(LDFLAGS) $(CFLAGS)
$(TARGET_FLAGS) -O3
It should not add target flags if we are simulating the target on the host.
On 06/06/2013 06:59 PM, reed kotler wrote:
> I want to get lnt to use qemu for the execution.
>
> In that case, RHOST= is not set.
>
> But I
2013 Sep 18
2
[LLVMdev] forcing two instructions to be together
I used the A9 schedule as an example:
http://llvm.org/svn/llvm-project/llvm/trunk/lib/Target/ARM/ARMScheduleA9.td
The documentation could use more clarity, but this is how I was able to do it to always get two specific instructions to be scheduled together.
________________________________________
From: reed kotler [rkotler at mips.com]
Sent: Tuesday, September 17, 2013 8:54 PM
To: Micah Villmow
2013 Sep 17
2
[LLVMdev] forcing two instructions to be together
Reed,
Couldn't you also use instruction scheduling classes and specify that the second instruction has a bypass from the first instruction? The scheduler should always schedule them together in that case.
Micah
> -----Original Message-----
> From: llvmdev-bounces at cs.uiuc.edu [mailto:llvmdev-bounces at cs.uiuc.edu] On
> Behalf Of reed kotler
> Sent: Tuesday, September 17, 2013
2013 Sep 17
2
[LLVMdev] forcing two instructions to be together
+the list again
On Sep 17, 2013, at 3:48 PM, reed kotler <rkotler at mips.com> wrote:
> On 09/17/2013 03:46 PM, Owen Anderson wrote:
>> On Sep 17, 2013, at 3:08 PM, reed kotler <rkotler at mips.com> wrote:
>>
>>> Is there any way, except for using bundles, to force two instructions to be sequentially executed?
>> What level of codegen are you working at?
2012 Sep 26
5
[LLVMdev] mips16 puzzle
We already divided out our classes as you did for ARM.
The problem here is that we have a store/load byte/halfword to/from a
Frame object.
We know at that time that it's not going to be possible to store it
using SP because there is only such instructions for store/load of a word.
What we would want to do is to move SP into a Mips 16 register and then
do a indexed load/store off of that
2013 Sep 18
0
[LLVMdev] forcing two instructions to be together
On 09/17/2013 04:51 PM, Micah Villmow wrote:
> Reed,
> Couldn't you also use instruction scheduling classes and specify that the second instruction has a bypass from the first instruction? The scheduler should always schedule them together in that case.
>
> Micah
>
I'm not sure exactly what you mean.
Can you point me to an example of that?
TIA.
Reed
>>
2013 Sep 18
0
[LLVMdev] forcing two instructions to be together
That doesn't actually give you a guarantee that they won't be split up. Phases other than the scheduler may insert instructions in the middle of block (constant island pass, for example). Pseudo-instructions are the canonical answer to that problem.
--Owen
On Sep 17, 2013, at 11:09 PM, Micah Villmow <micah.villmow at smachines.com> wrote:
> I used the A9 schedule as an
2012 May 14
3
[LLVMdev] getMinimalPhysRegClass
On 05/14/2012 02:42 PM, Jakob Stoklund Olesen wrote:
> On May 14, 2012, at 2:28 PM, reed kotler wrote:
>
>> I'm not using getMinimalPhysRegClass. Some target independent code is using it.
> Probably PEI.
>
>> It makes trouble for us and I would like to submit a patch to make it a virtual function so that I can override it and make it meaningful for Mips, as long as this
2012 Sep 26
0
[LLVMdev] mips16 puzzle
Ok. That's a somewhat different problem, then. Devil will be in the details of what you want to do. A few options. First is to always have a standard frame pointer register available and reference off of that. Caveat: dynamic stack realignment and vararrays muck with that more than a bit. Second is what gcc is doing and reserve a register just for this in addition to the frame register.
2012 May 14
0
[LLVMdev] getMinimalPhysRegClass
Reed,
On May 14, 2012, at 3:45 PM, reed kotler <rkotler at mips.com> wrote:
> On 05/14/2012 02:42 PM, Jakob Stoklund Olesen wrote:
>> On May 14, 2012, at 2:28 PM, reed kotler wrote:
>>
>>> I'm not using getMinimalPhysRegClass. Some target independent code is using it.
>> Probably PEI.
>>
>>> It makes trouble for us and I would like to
2013 Sep 17
0
[LLVMdev] forcing two instructions to be together
On 09/17/2013 03:52 PM, Owen Anderson wrote:
> +the list again
> On Sep 17, 2013, at 3:48 PM, reed kotler <rkotler at mips.com> wrote:
>
>> On 09/17/2013 03:46 PM, Owen Anderson wrote:
>>> On Sep 17, 2013, at 3:08 PM, reed kotler <rkotler at mips.com> wrote:
>>>
>>>> Is there any way, except for using bundles, to force two instructions to be
2012 Dec 13
2
[LLVMdev] failures in test-suite for make TEST=simple
The first one failed on a diff:
******************** TEST (simple) 'sse.expandfft' FAILED!
********************
Execution Context Diff:
/home/rkotler/llvmpb3/build/projects/test-suite/tools/fpcmp: Compared:
1.139094e-07 and 1.159249e-07
abs. diff = 2.015500e-09 rel.diff = 1.738626e-02
Out of tolerance: rel/abs: 1.600000e-02/0.000000e+00
******************** TEST (simple)
2012 Dec 13
1
[LLVMdev] failures in test-suite for make TEST=simple
I use the 'make TEST=simple' as a pre-commit test. I think that everybody should run these tests before committing to LLVM.
On Dec 12, 2012, at 5:06 PM, reed kotler <rkotler at mips.com> wrote:
> when I create the report, there are no failures in it. so maybe these are being filtered for known failures.
>
> On 12/12/2012 05:03 PM, reed kotler wrote:
>> The first
2012 Sep 21
2
[LLVMdev] mips16 puzzle
Actually, SP is already not in the mips 16 register class but there is
some C++ code that is common to mips32, mips64 and mips16 that is
wanting to use SP. It's kind of awkward but does work except in this
case of load/store haflword and byte to stack objects.
Maybe I'm shooting myself in the foot there. I don't know that code too
well so maybe I need to look into it.
There are
2012 Sep 06
2
[LLVMdev] micro mips/mips32
The problem is that everything about the mips32 and micro mips 16
instruction is the same, aside from the encoding in to binary.
Seems like maybe we need to extend the notion of an instruction so that
it can have alternate encodings depending on subtarget.
On 09/05/2012 08:28 PM, Jim Grosbach wrote:
> The instructions are defined by their encodings, not the assembly syntax. You want
2012 Dec 13
0
[LLVMdev] failures in test-suite for make TEST=simple
when I create the report, there are no failures in it. so maybe these
are being filtered for known failures.
On 12/12/2012 05:03 PM, reed kotler wrote:
> The first one failed on a diff:
> ******************** TEST (simple) 'sse.expandfft' FAILED!
> ********************
> Execution Context Diff:
> /home/rkotler/llvmpb3/build/projects/test-suite/tools/fpcmp: Compared:
>