Displaying 20 results from an estimated 100 matches similar to: "[LLVMdev] Data sharing between two ALUs and avoiding illegal copies"
2013 Jun 24
2
[LLVMdev] Register Class assignment for integer and pointer types
On Sun, Jun 23, 2013 at 04:57:44PM +0100, David Chisnall wrote:
> Hi,
>
> In our version of LLVM, we've added different-sized iPTR* types, so we have an iPTR256 for our fat pointers. This causes some problems with constraints, because the way that TableGen resolves constraints is not expected to handle multiple pointer types. We've added a flag that can be set on a per-backend
2020 May 29
2
Dynamically determine the CostPerUse value in the register allocator.
[AMD Official Use Only - Internal Distribution Only]
Hi All,
For the AMDGPU architecture, during RA, we prefer to have a cost associated with the registers (CostPerUse) based on a target entity (for instance, the Calling Convention of the current MachineFunction).
Presently CostPerUse is a one-time static value (either zero or a positive value) generated through table-gen.
The current
2020 May 30
2
Dynamically determine the CostPerUse value in the register allocator.
I dont know the history behind CostPerUse word so I may be missing the
background associated with it. It seems that it's misnomer for what it is
intended. At first sight, the word indicates that the cost is a function of
uses of the register - more the uses more the cost. How do we want to
define the value of CostPerUse. Should it be a function of uses? or just
the target?
On Sat, May 30,
2020 Nov 19
1
Problems with undef subranges in identity copies
Hi,
I'm stuck trying to fix a variety of problems that occur with undef
subregisters when the register coalescer eliminates identity
copies. The fundamental problem is complexity from the fact that undef
values are a special case since they don't have an associated
VNInfo/Segment unless the value is used across blocks.
For example, in this case, %0 has 2 subregisters sub0 and sub1:
2013 Oct 10
2
[LLVMdev] [PATCH] R600/SI: Embed disassembly in ELF object
Hi,
This patch adds R600/SI disassembly text to compiled object files, when
a code dump is requested, to assist debugging in Mesa clients.
Here's an example of the output in a Mesa client with a corresponding
patch and RADEON_DUMP_SHADERS set:
Shader Disassembly:
S_WQM_B64 EXEC, EXEC ; BEFE0A7E
S_MOV_B32 M0, SGPR6 ; BEFC0306
2016 Aug 23
2
How to describe the RegisterInfo?
Yes, the arch is just as you said, something like AMD GPU, but Intel GPU
don't have separate register file for 'scalar/vector'.
In fact my idea of defining the register tuples was borrowed from
SIRegisterInfo.td in AMD GPU.
But seems that AMD GPU mainly support i32/i64 register type, while Intel
GPU also support byte/short register type.
So I have to start defining the registers from
2013 Oct 10
0
[LLVMdev] [PATCH] R600/SI: Embed disassembly in ELF object
On Wed, Oct 09, 2013 at 08:06:42PM -0500, Jay Cornwall wrote:
> Hi,
>
> This patch adds R600/SI disassembly text to compiled object files, when
> a code dump is requested, to assist debugging in Mesa clients.
>
> Here's an example of the output in a Mesa client with a corresponding
> patch and RADEON_DUMP_SHADERS set:
>
> Shader Disassembly:
>
>
2018 Dec 20
2
RegBankSelect complex value mappings
Hi,
I’m looking at RegBankSelect’s partially implemented support for deciding to split a value between multiple registers and I’m wondering if it’s actually intended to solve the problem I’m trying to use it for. RegisterBankInfo.h has this example mapping table:
/// E.g.,
/// Let say we have a 32-bit add and a <2 x 32-bit> vadd. We
/// can expand the
/// <2 x 32-bit> add into
2016 Aug 23
2
How to describe the RegisterInfo?
Hi Escha,
Great to have your comment! Do you have any specific reason for not doing
like this?
I am not sure whether I understand your point correctly. For "just model
one thread",
do you mean "only considering ONE of the 8/16 working lanes that running in
lock-step way"??
For my case, may be something like I only need to define r0~r127 as
register for i32 register (each r#
2013 Jun 23
0
[LLVMdev] Register Class assignment for integer and pointer types
Hi,
In our version of LLVM, we've added different-sized iPTR* types, so we have an iPTR256 for our fat pointers. This causes some problems with constraints, because the way that TableGen resolves constraints is not expected to handle multiple pointer types. We've added a flag that can be set on a per-backend basis to turn this off.
Our problem is perhaps a bit different form yours,
2013 Jun 23
3
[LLVMdev] Register Class assignment for integer and pointer types
David, thanks for your immediate response.
Since iPTR is a reserved type for tablegen internal use, can you make a
further explanation?
On the other hand, it can be simply treated as a register class assignment
problem during register allocation.
Assume both pointer and integet have a 32 bit width. backend handles it
just as to i32. When it performs register allocation, it can retrieve from
2006 Apr 22
0
Major internal changes, TI DSP build change
Jean Marc,
>> The C5x and C6x output diverges in build 10143, which has log message
>> "lpc
>> floor converted to fixed-point." Also, the measured SNR changed from
>> 11.05
>> in builds 9854-10141 to 9.22 and 9.24 in 10143.
>
>Actually, build 10143 introduced another bug, that was the reason for
>the 1.1.11.1 release.
>
>> There is just
2006 Apr 22
0
Major internal changes, TI DSP build change
Jean-Marc,
>> >I fixed it in svn. Could you check that?
>>
>> Now all platforms match again. Note that the measured SNR for this test
>> sample is lower than with the broken code (10.87 vs 11.10), but of course
>> this is no way to judge the real quality.
>
> SNR, especially on a single sample, can be very misleading. Yet, could
> you just check that the
2006 Apr 22
2
Major internal changes, TI DSP build change
> >I fixed it in svn. Could you check that?
>
> Now all platforms match again. Note that the measured SNR for this test
> sample is lower than with the broken code (10.87 vs 11.10), but of course
> this is no way to judge the real quality.
SNR, especially on a single sample, can be very misleading. Yet, could
you just check that the DSP results match what you get on a PC?
2004 Oct 21
0
[LLVMdev] Re: LLVM Compiler Infrastructure Tutorial
Yiping,
If you are doing architectural synthesis, I do agree that you likely
need to capture some operations in the instruction set, especially if
you want to perform analyses and optimizations on those operations.
Some specific comments:
On Oct 20, 2004, at 6:04 PM, Yiping Fan wrote:
> Vikram,
> I also agree with you. I understand that target-independent
> representation is
2003 Sep 11
0
Perl module
I recently undertook the task of adding "Write" support to the Perl
module Ogg::Vorbis::Header::PurePerl (because of the simplicity of cross
platform use). Seeing as this list would have the most knowledge about
the proper methods regarding this task, I'm submitting this for anyone
to look at before it (possibly) hits CPAN.
http://alus.mine.nu/aRanger/PurePerl.pm
Any feedback would
2001 Sep 27
2
nightly cvs?
I wanted to ask if it is safe to encode my files with encoder compiled from nightly CVS archive?
--
Pagarbiai, Algirdas Kepeþinskas
[algis@kitoks.lt] [QQuxa@irc.delfi.lt] [UIN 14187537]
/ Padariau zodyje MAMA keturias klaidas... gavosi ALUS /
--- >8 ----
List archives: http://www.xiph.org/archives/
Ogg project homepage: http://www.xiph.org/ogg/
To unsubscribe from this list, send a message
2003 Sep 09
1
Checksum question
I'm trying to simply regenerate the comment header checksum on the ogg
file "test.ogg"
I ripped the checksum function from libvorbis, and only modified it in
that I hard-coded what I think is the comment header (as far as I can
tell from the docs). However it seems to generate an invalid checksum
(according to ogginfo)
Here is a url to the two files, please help :)
2004 Oct 20
2
[LLVMdev] Re: LLVM Compiler Infrastructure Tutorial
Vikram,
I also agree with you. I understand that target-independent representation is very valuable
and important for software compilation.
However, when we are doing high-level synthesis (also called behavioral/architectural synthesis),
the targeting architecture is also changing. That is, we need to do architecture exploration
and the IR transfromation simultaneously. For example,
2017 Nov 03
2
RFC: [X86] Introducing command line options to prefer narrower vector instructions even when wider instructions are available
On Thu, Nov 2, 2017 at 7:05 PM James Y Knight via llvm-dev <
llvm-dev at lists.llvm.org> wrote:
> On Wed, Nov 1, 2017 at 7:35 PM, Craig Topper via llvm-dev <
> llvm-dev at lists.llvm.org> wrote:
>
>> Hello all,
>>
>>
>>
>> I would like to propose adding the -mprefer-avx256 and -mprefer-avx128
>> command line flags supported by latest GCC to