similar to: Recursive filetype include

Hello, I have a problem with a NAS. I have mounted the NAS with : smbmount //ip_nas//folder_name /mnt/disque When i list the content of this folder (ls -l /mnt/disque), i have this message : smb_filetype_to_mode : filetype out of range : 12336 It lists the folder with strange names, for instance : 5?? cationd r ???? The biggest file in this folder is an image disc file of 2Gbytes. Thanks for

Jim, I see routines that are already available to do the endianizing, but the data and text section contents don't have sizing for the individual elements as far as I can see so that I can endianize them. That is the part I am trying to solve, not the bit twiddling algorithm. Did I miss something? Jack ________________________________________ From: Jim Grosbach [grosbach at apple.com] Sent:

Hi Jack, I would have expected the Mips backend to be using these routines (or more likely something on top of them) to emit the contents of the data and text sections and thus have the bit-twiddling done by these routines. I take it that's not happening? Basically, this should already work without any additional infrastructure. If it's not, something is broken and bypassing the

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I mentioned a ghost file. Here is the dump (less than 65M): http://dev.mccme.ru/~raskin/btrfs.dump ghost file is: 885dj1l4788pymp3bk2f3dz52ggcvw4v-empty/garbage-1/mwave.h.tmp-31838-1822528541 It has a name, but stat fails (so no inode, I guess). Also I can create another file with the same name in the directory. I cannot remove the file, or

Hello, I use a windows program in Wine that opens images in another program. I know that in WIndows, it uses the default program associated with the filetype. However in Ubuntu, the process started when I click on an image is "C:\Program Files\Internet Explorer\iexplore.exe -nohome" So I see no image. I have tried launching manually iexplore with the image path as parameter, and it

Is there a way in R (in Linux) to detect the type of a file without invoking a shell? E.g to do this: > system("file density.plot") density.plot: PDF document, version 1.4 but without using system()? I tried file() and file.info(), but both do display the information I am looking for. -- View this message in context:

Hello! I am working with LLVM project to compile for specific processor (xPEC-processor from NetX chip, http://hilscher.com/ ). I have done support of this target successfully! Assembler code can be emitted with debug information. LLVM - great!) But now I am looking for generation of machine code for my target. I have seen, that "llc" has option "-filetype". It has

On Mon, Jul 27, 2009 at 8:25 AM, Rudskyy<tema13tema at yahoo.de> wrote: > But now I am looking for generation of machine code for my target. I have > seen, that “llc” has option "-filetype". > > It has default value "-filetype=asm", but has more values, as > "-filetype=obj" and "-filetype=dynlib". > > “obj” is very interesting, but

Chris Lattner wrote: > On Mar 27, 2010, at 11:56 AM, Peter Shugalev wrote: > >>>> What exactly is expected to be coming? Will it be the same way MachO is >>>> currently implemented but with some flexibility to supply my own class >>>> to do actual object output? Or just a return of old ObjectCodeEmitter? >>> We're integrating a full assembler

Hi Jack, Everything should be already using the sized Emit* routines directly rather than outputting individual bytes of larger entities piecemeal. Have you found that not to be the case? The Emit* routines handle endianness for you, so you shouldn't have to do much beyond that. For example, here's the EmitInvValue() implementation that underlies things and does the endianness transform:

On Mar 27, 2010, at 11:56 AM, Peter Shugalev wrote: >>> What exactly is expected to be coming? Will it be the same way MachO is >>> currently implemented but with some flexibility to supply my own class >>> to do actual object output? Or just a return of old ObjectCodeEmitter? >> >> We're integrating a full assembler into the compiler. I'm not sure

Hi Jack, On Sat, Mar 2, 2013 at 8:15 AM, Jack Carter <Jack.Carter at imgtec.com> wrote: > Jia, > > I made what I believe to be the correct changes and rebuilt clang and llc. Are the results what you expected? I so I will prepare the patches for commitment. > > Jack > > clang ../mips_R_JiaLiu.c -o mips_R_JiaLiu.ll -emit-llvm -O3 -S -target mipsel-unknown-linux -std=gnu89

Sorry in advance for the stupid question, i still don’t understand some concepts like passes. I took a piece of code from llc, and I used it to write a function that creates an object (or assembly) file from an IR module. It compiles without any problems. But program crashes when it reaches add() method of the pass manager. Can you help me figuring out what’s the problem please? here is my

Alrighty, Got it patched and working (at least in my one setup). You can pull the patch from: http://denetron.com/~dballenger/ezstream-program.patch (I can post the pre-patched source too if people would like) You'll have to add a "<filetype></filetype>" line into your config files, just put "file" if you want it to work just by reading that file or playlist.

Proposal for ELF text and data big endian support for direct object generation Unless I am mistaken, currently big endian support in the MC layer for ELF direct object generation is limited to ELF headers and tables like relocations. Text and data section contents are still generated as individual bytes. It looks as if the effort was started, but never completed. The proposal is to extend the

Hello, I'm eager to get to know Clang+LLVM but I'm having some problems generating debug information that force llc.exe to crash. I'm running from the command-line on Windows 7 with clang+llvm versions 2.9 downloaded from the website. The input file is main.c:      void mainCRTStartup()      {      } This is compiled to intermediate with debug symbols using:      clang -g -O0 -c

Consider the following function which doubles a <16 x i8> vector: define <16 x i8> @test(<16 x i8> %a) { %b = add <16 x i8> %a, %a ret <16 x i8> %b } If I compile it for x86 with llc like so: llc paddb.ll -filetype=asm -o=/dev/stdout I get a two-op function that just does paddb %xmm0 %xmm0 and then returns. llc does this regardless of the

The llvm ARM backend is little endian elf output as my examination as below. Is it support bid endian by other llc options as below? llc  -filetype=obj -march=arm // little endian llc  -filetype=obj -march=? or -otheroption=? // to output big endian Jonathan -------------- next part -------------- An HTML attachment was scrubbed... URL:

Assuming you are talking about this line: passmanager.add(tliwp); I don't see anything obviously wrong. Are you hitting an assertion or a pure crash? (if LLVM not built with assertions, please rebuild). What does your debugger gives you as a stracktrace? -- Mehdi > On Mar 23, 2016, at 3:44 PM, Lorenzo Laneve via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > Sorry in

Hi, I'm using ext3 filesystems in embedded devices (storage is on 512Mb or 1Gb CF cards). A typical development cycle would see the filesystem created on the desktop PC running linux 2.4 (eg. RedHat 9). The CF card would be installed in the hardware and linux 2.4 (eg. Montavista Pro 3.1, on PPC) would boot from the CF. Recently I tried a linux 2.6 desktop (CentOS) for the same task and