similar to: [LLVMdev] bug? c backend produces code rejected by gcc4.0.1: array type has incomplete element type

It seems very similar to http://llvm.org/bugs/show_bug.cgi?id=737 . You might want to check if it's the same problem. If not, then please create a new bug report. -bw On 9/20/06, Samuele Pedroni <pedronis at strakt.com> wrote: > The C backend can currently (recent head) produce code with such patterns: > > /* Global Declarations */ > /* Structure forward decls */ >

On Wed, 20 Sep 2006, Samuele Pedroni wrote: > The C backend can currently (recent head) produce code with such patterns: > gcc 4.0.1 will reject this with > example.c:7: error: array type has incomplete element type > > this kind of code was accepted by previous versions of gcc as a fragile > extension, but is no longer at least in 4.0.1 . > > is this known? should I file

Hello, I would like to ask the llvm developers to have a look at http:// llvm.org/bugs/show_bug.cgi?id=918 . This bug has been reported 4 month ago but is none the less a somewhat serious one. Below I have pasted the test case and output of the issue running on my ppc machine. thank you Eric pb:~ eric$ cat testme.ll;llvm-as -f testme.ll;llc -march=c -f testme.bc;gcc -c testme.cbe.c

Eric van Riet Paap wrote: > *testme.cbe.c:106: error: array type has incomplete element type* The problem code boils down to: /* Structure forward decls */ struct l_structtype_s; /* Typedefs */ typedef struct l_structtype_s l_fixarray_array3[3]; which is illegal C, but perfectly valid C++, and g++ accepts it. The structure contents are defined right afterwards, but I assume that

On Mon, 15 Jan 2007, Nick Lewycky wrote: > Eric van Riet Paap wrote: >> *testme.cbe.c:106: error: array type has incomplete element type* > > The problem code boils down to: > > /* Structure forward decls */ > struct l_structtype_s; > > /* Typedefs */ > typedef struct l_structtype_s l_fixarray_array3[3]; > > which is illegal C, but perfectly valid C++,

On Tue, 16 Jan 2007, Gordon Henriksen wrote: > The simplest solution is to avoid typedefs for array types. With > names of array types removed from the symbol table, llc will simply > output (for instance) 'l_structtype_s[3]' instead of the equivalent > 'l_fixarray_array3'. Very nice catch and approach. > A more ambitious fix would be to merge the

On 2007-01-15, at 11:48, Chris Lattner wrote: > On Mon, 15 Jan 2007, Nick Lewycky wrote: > >> The structure contents are defined right afterwards, but I assume >> that the typedefs are used when emitting the structure contents? >> We may have to put fully defined structures first and typedefs >> second. > > Looks like it. It sounds like the CBE should

Hi, On Nov 13, 2006, at 9:17 PM, Tanya M. Lattner wrote: > I assume you have an Mac with an Intel processor. Yes. Sorry, I forgot to mentioned it in the mailbody. > Download this: > http://llvm.org/releases/1.8/llvm-gcc4-1.8-x86-darwin.tar.gz I think that is the same tarball I used before. > Let me know if that doesn't work. Again: there is no fixheader-script like you

> I wanted to install llvm 1.8 and the frontend at my MacBook Pro but I > think the gcc4 frontend doesn't work (gcc3 and llvm 1.8 works fine on > my old ppc-based mac). There are no fixheaders-script and no include > directories ... > Are there working gcc 4 binaries? Did I miss some informations on the > llvm-webpage? > Or do I have to build my own gcc frontend? I assume

Hi, I wanted to install llvm 1.8 and the frontend at my MacBook Pro but I think the gcc4 frontend doesn't work (gcc3 and llvm 1.8 works fine on my old ppc-based mac). There are no fixheaders-script and no include directories ... Are there working gcc 4 binaries? Did I miss some informations on the llvm-webpage? Or do I have to build my own gcc frontend? Thank you Nico

Great! Please let the mailing list know if you run into any further problems. -- Peter Paolo Pedroni wrote: > > Alle 16:38, venerd=EC 25 agosto 2006, hai scritto: > > Paolo, > > > > I recently fixed some bugs regarding the report descriptor retrieval. > > Please try it with the newest development version from SVN. You can > > follow the instructions at >

>> I assume you have an Mac with an Intel processor. > > Yes. Sorry, I forgot to mentioned it in the mailbody. > >> Download this: >> http://llvm.org/releases/1.8/llvm-gcc4-1.8-x86-darwin.tar.gz > > I think that is the same tarball I used before. Ok. I'm confused. Do you want llvm-gcc3 or llvm-gcc4? The tarball above is a binary for llvm-gcc4 for Mac x86. You

Whenever I try to use the newhidups driver with my new UPS I get the following message: #/lib/nut/newhidups -DDD -a SmartUps1500 Network UPS Tools: New USB/HID UPS driver 0.28 (2.0.4) debug level is '3' [...skip unrelevant device...] Checking device (051D/0002) (001/005) - VendorID: 051d - ProductID: 0002 - Manufacturer: American Power Conversion - Product: Smart-UPS 1500 FW:601.3.I USB

How can I suppress this warning? > options(warn = -10) > list(1,2,3,) Warning: a final empty element has been omitted the part of the args list of 'list' being evaluated was: (1, 2, 3, ) [[1]] [1] 1 [[2]] [1] 2 [[3]] [1] 3 > suppressWarnings(list(1,)) Warning: a final empty element has been omitted the part of the args list of 'list' being evaluated was: (1, )

Hello, after I wasn''t able to install wxruby via gem (404) I downloaded the file from rubyforge and installed it on my intel mac. No failure the so I tried to start the minimal.rb with ruby -r/r?/ ubegems <path>... This didn''t work so I tried to do it in irb but the same error occured: irb(main):001:0> require ''rubygems'' => true

I followed Duncan Davidson''s Sandboxing Rails with Darwin Ports guide and everything went fine up till the part where I had to install gems using gem install. I would get this stacktrace: Attempting local installation of ''rake'' Local gem file not found: rake*.gem Attempting remote installation of ''rake''

Hi, Just downloaded the new ferret 0.11. I''m on OSX btw. I get this error everytime I run my unit tests: Loaded suite ferret_updater_unit_test Started E/usr/local/lib/ruby/1.8/erb.rb:504: [BUG] Segmentation fault ruby 1.8.4 (2005-12-24) [i686-darwin8.7.1] Abort trap When I revert back to 10.14 I dont get this error. When I comment out the line: Ferret::Index::Index.new({:path =>

Paolo, Try sudo /lib/nut/newhidups -DDD -u root -a SmartUps1500 newhidups would only run on my computer if I ran it using sudo and as root user. I know this indicates a problem with the USB permissions, but I could not, for the life of me, get the permissions to change when I plugged the UPS in. I know this isn't a true fix, but it worked for me. -- ~Brian Foster

Heya Folks- This is mainly for Zed and Mentalguy. I have been playing with the new release of rubygems 0.9.0.8 and I have a major problem with the requirement that fastthread needs to be required before thread. Just requiring rubygems and then requiring fastthread right after that will throw the error: ez _blog $ ruby require ''rubygems'' require

Hi all, I'm thoroughly stumped. I have a network of Windows 2k and Windows XP Professional machines working off of Samba served home directories. Everything works. Sign-ons are relatively quick, no odd errors in the samba logs or on the Windows boxes, and all the configuration seems to work fine wrt all functions. Name lookups via nmblookup or nbtstat work fine (though it looks like