search for: bitfield

...the NVFXTCL_ approach is worthwhile. If consensus develops against this notion, it is easy to change the Python script that generated the unification patch and rerun it. Luca Barbieri (5): renouveau: completely describe POINT_SPRITE on nv30 and nv40 renouveau/nv40: describe CLEAR_VALUE_COLOR bitfields renouveau/nv40: set NV40TCL_LINE_STIPPLE_PATTERN to hexa like nv30 renouveau/nv30: remove clip planes #6 and #7 renouveau: unify nv30 and nv40 as NVFXTCL nvfx.py | 207 +++++++++++++ nvfx.sed | 340 ++++++++++++++++++++++ renouveau.xml | 891 ++++++++++++++++++++++------------...

...at luca-barbieri.com> --- renouveau.xml | 49 ------------------------------------------------- 1 files changed, 0 insertions(+), 49 deletions(-) diff --git a/renouveau.xml b/renouveau.xml index 8fb35a5..3fb9d9a 100644 --- a/renouveau.xml +++ b/renouveau.xml @@ -2498,55 +2498,6 @@ <bitfield name="STRIDE" high="15" low="8" type="int"/> <bitfield name="POS_HOMOGENEOUS" high="24" low="24" type="boolean"/> </reg32> - - <reg32 offset="0x0d00" name="VERTEX_ARRAY_OF...

Hi, This is my work in documenting EVO. I did some RE to fill missing gaps. Best regards, Maxim Levitsky

...pramdac.xml | 67 +++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 67 insertions(+) diff --git a/rnndb/display/nv3_pramdac.xml b/rnndb/display/nv3_pramdac.xml index 13b6a7b..e236921 100644 --- a/rnndb/display/nv3_pramdac.xml +++ b/rnndb/display/nv3_pramdac.xml @@ -79,12 +79,79 @@ <bitfield pos="28" name="VCLK_DB2"/> <bitfield pos="29" name="VCLK2_DB2" variants="NV11:NV20 NV25:G80"/> </reg32> + <reg32 offset="0x510" name="PLL_SETUP_CONTROL"/> <reg32 offset="0x520" name="...

...++++++++++--- > 1 file changed, 34 insertions(+), 3 deletions(-) > > diff --git a/rnndb/memory/nvc0_pbfb.xml b/rnndb/memory/nvc0_pbfb.xml > index 500cea9..e006dbe 100644 > --- a/rnndb/memory/nvc0_pbfb.xml > +++ b/rnndb/memory/nvc0_pbfb.xml > @@ -49,23 +49,54 @@ > Most bitfields are unknown. > </doc> > <bitfield high="7" low="0" name="RP"> > - <doc> RAS# precharge. </doc> > + <doc> RAS# Precharge. </doc> > </bitfield> > <bitfield high="15" low="...

...t/llvm/projects/test-suite/include -I../../include -I/home/jay/llvm/gitobjdir/include -I/home/jay/git/llvm/include -D_GNU_SOURCE -D__STDC_LIMIT_MACROS -DNDEBUG -O3 -mllvm -disable-llvm-optzns -m64 -fomit-frame-pointer -S /home/jay/svn/llvm-project/test-suite/trunk/SingleSource/UnitTests/ms_struct-bitfield-init-1.c -o Output/ms_struct-bitfield-init-1.ll -emit-llvm /home/jay/svn/llvm-project/test-suite/trunk/SingleSource/UnitTests/ms_struct-bitfield-init-1.c:28: error: size of array ‘a3’ is negative make[3]: [Output/ms_struct-bitfield-init-1.ll] Error 1 (ignored) /home/jay/llvm/gitobjdir/Release+Asser...

...] 254 iProduct Item(Local ): String Index, data= [ 0x02 ] 2 Item(Main ): Feature, data= [ 0x23 ] 35 Constant Variable Absolute No_Wrap Linear No_Preferred_State No_Null_Position Non_Volatile Bitfield Item(Global): Report ID, data= [ 0x02 ] 2 Item(Local ): Usage, data= [ 0xff ] 255 iSerialNumber Item(Local ): String Index, data= [ 0x03 ] 3 Item(Main ): Feature, data= [ 0x23 ] 35 Constant Vari...

...c0_pbfb.xml | 37 ++++++++++++++++++++++++++++++++++--- 1 file changed, 34 insertions(+), 3 deletions(-) diff --git a/rnndb/memory/nvc0_pbfb.xml b/rnndb/memory/nvc0_pbfb.xml index 500cea9..e006dbe 100644 --- a/rnndb/memory/nvc0_pbfb.xml +++ b/rnndb/memory/nvc0_pbfb.xml @@ -49,23 +49,54 @@ Most bitfields are unknown. </doc> <bitfield high="7" low="0" name="RP"> - <doc> RAS# precharge. </doc> + <doc> RAS# Precharge. </doc> </bitfield> <bitfield high="15" low="8" name="RAS"> -...

...-suite/include -I../../include > -I/home/jay/llvm/gitobjdir/include -I/home/jay/git/llvm/include > -D_GNU_SOURCE -D__STDC_LIMIT_MACROS -DNDEBUG  -O3 -mllvm > -disable-llvm-optzns  -m64 -fomit-frame-pointer -S > /home/jay/svn/llvm-project/test-suite/trunk/SingleSource/UnitTests/ms_struct-bitfield-init-1.c > -o Output/ms_struct-bitfield-init-1.ll -emit-llvm > /home/jay/svn/llvm-project/test-suite/trunk/SingleSource/UnitTests/ms_struct-bitfield-init-1.c:28: > error: size of array ‘a3’ is negative If I compile this test by hand, I get the same error: $ llvm-gcc -c ms_struct-bitfield...

Hi Guillaume, Thanks for the RFC. I'm generally +1 on the concept. Making bit field manipulation easier seems like a good overall goal given its prevalence in LLVM. As for the syntax, I tend to prefer that we don't pollute the namespace. Have you considered pushing the methods into the Bitfield class? Maybe something like: ``` uint8_t Storage = 0; using Amount = Bitfield::Element<unsigned, 0, 4>; Bitfield::set<Amount>(Storage, true); unsigned Value = Bitfield::get<Amount>(Storage); bool Cond = Bitfield::test<Amount>(Storage); ``` ^ Seems good to me bec...

...-suite/include -I../../include > -I/home/jay/llvm/gitobjdir/include -I/home/jay/git/llvm/include > -D_GNU_SOURCE -D__STDC_LIMIT_MACROS -DNDEBUG -O3 -mllvm > -disable-llvm-optzns -m64 -fomit-frame-pointer -S > /home/jay/svn/llvm-project/test-suite/trunk/SingleSource/UnitTests/ms_struct-bitfield-init-1.c > -o Output/ms_struct-bitfield-init-1.ll -emit-llvm > /home/jay/svn/llvm-project/test-suite/trunk/SingleSource/UnitTests/ms_struct-bitfield-init-1.c:28: > error: size of array ‘a3’ is negative > make[3]: [Output/ms_struct-bitfield-init-1.ll] Error 1 (ignored) > /home/jay/llv...

...8G8B8 Ch 1/5 Class 0x0597 Mthd 0x0208 Data 0x01000100:0x00000108 Ch 1/5 Class 0x0597 Mthd 0x0208 Data 0x00800080:0x00000108 The only value I found in renouveau dump was 0x00000128. Let's look at renouveau.xml nv20 <reg32 offset="0x0208" name="RT_FORMAT" type="bitfield"> <bitfield name="TYPE" high="11" low="8" type="enum" enum_name="nv40_rendertarget_type"/> <bitfield name="COLOR" high="4" low="0" type="enum" enum_name="nv40_rendertarget_col...

...): Logical Maximum, data= [ 0xff 0x00 ] 255 Item(Global): Logical Minimum, data= [ 0x00 ] 0 Item(Main ): Feature, data= [ 0x03 ] 3 Constant Variable Absolute No_Wrap Linear Preferred_State No_Null_Position Non_Volatile Bitfield Item(Global): Report ID, data= [ 0x29 ] 41 Item(Local ): Usage, data= [ 0xff ] 255 iSerialNumber Item(Main ): Feature, data= [ 0x03 ] 3 Constant Variable Absolute No_Wrap Linear...

...s.llvm.org> wrote: >> >> On 28 May 2020, at 18:42, Bill Wendling wrote: >> >> > On Tue, May 26, 2020 at 7:49 PM James Y Knight via llvm-dev >> > <llvm-dev at lists.llvm.org> wrote: >> >> >> >> At least in this test-case, the "bitfield" part of this seems to be a >> >> distraction. As Eli notes, Clang has lowered the function to LLVM IR >> >> containing consistent i16 operations. Despite that being a different >> >> choice from GCC, it should still be correct and consistent. >> >&...

...ogical Maximum, data= [ 0xff 0x00 ] 255 Item(Global): Logical Minimum, data= [ 0x00 ] 0 Item(Main ): Feature, data= [ 0x03 ] 3 Constant Variable Absolute No_Wrap Linear Preferred_State No_Null_Position Non_Volatile Bitfield Item(Global): Report ID, data= [ 0x29 ] 41 Item(Local ): Usage, data= [ 0xff ] 255 iSerialNumber Item(Main ): Feature, data= [ 0x03 ] 3 Constant Variable Absolute No_Wrap Linear...

On 28 May 2020, at 18:42, Bill Wendling wrote: > On Tue, May 26, 2020 at 7:49 PM James Y Knight via llvm-dev > <llvm-dev at lists.llvm.org> wrote: >> >> At least in this test-case, the "bitfield" part of this seems to be a >> distraction. As Eli notes, Clang has lowered the function to LLVM IR >> containing consistent i16 operations. Despite that being a different >> choice from GCC, it should still be correct and consistent. >> > I suspect that this is m...

We're running into an interesting issue with the Linux kernel, and wanted advice on how to proceed. Example of what we're talking about: https://godbolt.org/z/ABGySq The issue is that when working with a bitfield a load may happen quickly after a store. For instance: struct napi_gro_cb { void *frag; unsigned int frag_len; u16 flush; u16 flush_id; u16 count; u16 gro_remcsum_start; unsigned long age; u16 proto; u8 same_flow : 1; u8 encap_mark : 1; u8 csum_valid : 1...

...I../../include >> -I/home/jay/llvm/gitobjdir/include -I/home/jay/git/llvm/include >> -D_GNU_SOURCE -D__STDC_LIMIT_MACROS -DNDEBUG  -O3 -mllvm >> -disable-llvm-optzns  -m64 -fomit-frame-pointer -S >> /home/jay/svn/llvm-project/test-suite/trunk/SingleSource/UnitTests/ms_struct-bitfield-init-1.c >> -o Output/ms_struct-bitfield-init-1.ll -emit-llvm >> /home/jay/svn/llvm-project/test-suite/trunk/SingleSource/UnitTests/ms_struct-bitfield-init-1.c:28: >> error: size of array ‘a3’ is negative > > If I compile this test by hand, I get the same error: > > $...

On 03/09/2017 12:57 PM, Krzysztof Parzyszek wrote: > On 3/9/2017 12:47 PM, Hal Finkel wrote: >> >> On 03/09/2017 12:28 PM, Krzysztof Parzyszek via llvm-dev wrote: >>> We could add intrinsics to extract/insert a bitfield, which would >>> simplify a lot of that bitwise logic. >> >> But then you need to teach a bunch of places about how to simply them, >> fold using bitwise logic and other things that reduce demanded bits into >> them, etc. This seems like a difficult tradeoff. > &...

...wrote: > Hi, > > On 26/12/2019 20:53, Ehud Katz via llvm-dev wrote: > > I've tested it on MSVC, gcc, clang and icc. > > > > The solution in clang (in Decl.h) is not ideal (as you have said > yourself). The solution I offer, is using a union of fields of class > BitField (this is a new class that implements a bitfield of a specific type > requested). With this, the definition, of the required bitfields in the > subclass data, remains in the hands of the actual class needing them. And > these are all restricted hierarchically by the superclasses of that cla...