search for: parsegetelementptr

...without > making use of LLVM's API, which would error out sooner if I tried > this? Or is there a more fundamental reason why there's no better > error message? Is it useful to create a bug about this? I think it makes sense to create a bug report. Looking at the code of LLParser::ParseGetElementPtr, the error handling appears to be very simplistic, so I don't think there's any fundamental reason for not doing a better job there. Eli

On Wed, Jan 16, 2013 at 5:18 PM, Eli Bendersky <eliben at google.com> wrote: > I think it makes sense to create a bug report. Looking at the code of > LLParser::ParseGetElementPtr, the error handling appears to be very > simplistic, so I don't think there's any fundamental reason for not > doing a better job there. Filed http://llvm.org/bugs/show_bug.cgi?id=14965, thanks! Cheers, Dirkjan

On Wed, Jan 16, 2013 at 8:22 AM, Tim Northover <t.p.northover at gmail.com> wrote: > I get that error when the %str type is undefined (presumably because > LLVM doesn't know its alignment requirements so can't lay out the > array$str type properly). For example, the following complete program > works correctly for me: > > %str = type {i8*, i64} > %array$str =