search for: i80

On Mon, Jun 7, 2010 at 5:49 PM, Duncan Sands <baldrick at free.fr> wrote: > Hi Hao Shen, > >> Is there anyone who knows well i80 data type? Is there any >> corresponding data type >> for X86 processor? uint80_t or int80_t for gcc? > > no, there is no native processor support for i80. GCC does not have > a direct equivalent to i80. However if you declare a 80-bit wide C > bitfield, then arithmetic on...

Dear all, Is there anyone who knows well i80 data type? Is there any corresponding data type for X86 processor? uint80_t or int80_t for gcc? PS. I found that the LLVM website is down! -- Hao Shen

Hi Hao Shen, > Is there anyone who knows well i80 data type? Is there any > corresponding data type > for X86 processor? uint80_t or int80_t for gcc? no, there is no native processor support for i80. GCC does not have a direct equivalent to i80. However if you declare a 80-bit wide C bitfield, then arithmetic on it is done in 80 bits. Fo...

Hi Hao Shen, > OK, thanks a lot. I can understand how i80 works. > But why i80 appears in my byte-code? How to remove it > by using some passes? it may be created by the sroa (scalarrepl) pass which sometimes introduces such registers when 10 bytes are being loaded from memory. Why do you want to remove it? Ciao, Duncan.

...ts are below. cat /etc/udev/rules.d/90-local.rules KERNEL=="sg[0-9]*", SUBSYSTEM=="scsi_generic", \ ENV{ID_SERIAL}=="1QUANTUM_D0H0112430_LLA", SYMLINK+="sg8" SUBSYSTEM=="scsi", SUBSYSTEMS=="scsi_genric", \ ATTRS{model}=="Scalar i40-i80 ", SYMLINK:="sg8" Neither rule above generates a match with udev, so I still have something wrong. Right now the assignment is sg7 (but it's had other names in the past. udevadm info --query=all --name=/dev/sg7 P: /devices/pci0000:00/0000:00:07.0/0000:04:00.0/0000:05:00.0/...

...>> >> KERNEL=="sg[0-9]*", SUBSYSTEM=="scsi_generic", \ >> ENV{ID_SERIAL}=="1QUANTUM_D0H0112430_LLA", SYMLINK+="sg8" >> >> SUBSYSTEM=="scsi", SUBSYSTEMS=="scsi_genric", \ >> ATTRS{model}=="Scalar i40-i80 ", SYMLINK:="sg8" > > You have a typo: scsi_genric instead of scsi_generic. > > Don't know if that is the reason. > > Cheers > Tony >

...sg[0-9]*", SUBSYSTEM=="scsi_generic", \ >>>> ENV{ID_SERIAL}=="1QUANTUM_D0H0112430_LLA", SYMLINK+="sg8" >>>> >>>> SUBSYSTEM=="scsi", SUBSYSTEMS=="scsi_genric", \ >>>> ATTRS{model}=="Scalar i40-i80? ", SYMLINK:="sg8" >>> >>> You have a typo: scsi_genric instead of scsi_generic. >>> >>> Don't know if that is the reason. >>> > > > SYMLINK:="sg8" -> SYMLINK+="sg8" > > -- > Leon > >...

....18-274. On one server: # cat /proc/scsi/scsi Attached devices: Host: scsi0 Channel: 00 Id: 00 Lun: 00 Vendor: HP Model: Ultrium 5-SCSI Rev: Z58Z Type: Sequential-Access ANSI SCSI revision: 06 Host: scsi0 Channel: 00 Id: 00 Lun: 01 Vendor: QUANTUM Model: Scalar i40-i80 Rev: 135G Type: Medium Changer ANSI SCSI revision: 03 # mtx -f /dev/sg0 inquiry mtx: Request Sense: Long Report=yes mtx: Request Sense: Valid Residual=no mtx: Request Sense: Error Code=70 (Current) mtx: Request Sense: Sense Key=Illegal Request mtx: Request Sense: FileMark=n...

...ules.d/90-local.rules > > KERNEL=="sg[0-9]*", SUBSYSTEM=="scsi_generic", \ > ENV{ID_SERIAL}=="1QUANTUM_D0H0112430_LLA", SYMLINK+="sg8" > > SUBSYSTEM=="scsi", SUBSYSTEMS=="scsi_genric", \ > ATTRS{model}=="Scalar i40-i80 ", SYMLINK:="sg8" You have a typo: scsi_genric instead of scsi_generic. Don't know if that is the reason. Cheers Tony -- Tony Mountifield Work: tony at softins.co.uk - http://www.softins.co.uk Play: tony at mountifield.org - http://tony.mountifield.org

...; KERNEL=="sg[0-9]*", SUBSYSTEM=="scsi_generic", \ >>> ENV{ID_SERIAL}=="1QUANTUM_D0H0112430_LLA", SYMLINK+="sg8" >>> >>> SUBSYSTEM=="scsi", SUBSYSTEMS=="scsi_genric", \ >>> ATTRS{model}=="Scalar i40-i80 ", SYMLINK:="sg8" >> >> You have a typo: scsi_genric instead of scsi_generic. >> >> Don't know if that is the reason. >> SYMLINK:="sg8" -> SYMLINK+="sg8" -- Leon

Duncan, could this be related to your recent work? Chuck, this is unlikely to be a x86 specific problem. Please file a bug. Thanks! Evan On Dec 6, 2007, at 5:06 PM, Chuck Rose III wrote: > Hola LLVMers, > > One of the corner-case features of the Hydra language I work on are > Boolean vectors of length 2, 3, or 4 which I’ve been representing as > either <2 x i1> or

Hola LLVMers, One of the corner-case features of the Hydra language I work on are Boolean vectors of length 2, 3, or 4 which I've been representing as either <2 x i1> or <4 x i1>. I picked up the latest LLVM about a week back and since then I've been unable to compile things using this construct. It asserts in TargetData::getAlignmentInfo since it doesn't have

...align 2, !tbaa !5 %cmp5.7.i.i78.i.i.i = icmp eq i16 %133, 0 br i1 %cmp5.7.i.i78.i.i.i, label %for.inc.7.i.i81.i.i.i, label %if.end.i.i.i.i.i for.inc.7.i.i81.i.i.i: ; preds = %for.inc.6.i.i79.i.i.i %134 = load i16* %incdec.ptr.7.i55.i.i, align 2, !tbaa !5 %phitmp.i80.i.i.i = icmp eq i16 %134, 0 br i1 %phitmp.i80.i.i.i, label %eisneg.exit142.i.i.i, label %if.end.i.i.i.i.i eisneg.exit142.i.i.i: ; preds = %for.inc.7.i.i81.i.i.i %.lobit.i.i.i.i = lshr i16 %79, 15 %.lobit.i138.i.i.i = lshr i16 %98, 15 %cmp.i.i.i = icmp eq i16 %.l...