search for: pietrek

...>> shuffles object files around. > > Hi Krister, > > We've applied your patch locally and it solved our problem, thanks! ... but, as it was discussed earlier, it breaks Darwin. I applied a patch to handle DW_AT_stmt_list using target hook (based on original patch by Artur Pietrek). r112678. Please try it and let me know if it works. If it works, please prepare a patch for debug_range using similar target hook approach. - Devang

On Fri, Aug 21, 2009 at 12:33 PM, Eli Friedman <eli.friedman at gmail.com>wrote: > On Fri, Aug 21, 2009 at 2:02 AM, Artur Pietrek<pietreka at gmail.com> wrote: > > Hi All, > > Since few days I observe weird change. > > Consider the following C code > > > > char array[] = "0123456789"; > > extern int test(char arr[], int size); > > > > int main(void) { > >...

...ed completing the MSIL backend for running on Mono. Things that need to be fixed include pointers initialization, call to vararg functions, incorrect stack fill after some function calls, removal of unused local variables, use of the switch capabilities of MSIL and others. Best regards, Artur Pietrek

On Thu, Apr 15, 2010 at 3:40 AM, Artur Pietrek <pietreka at gmail.com> wrote: > Hi all > Ups, I'm really sorry for that previous message, I've sent it by mistake. > > So let me write it once more. > > I've been working for some time now on a backend for our CPU. However I > couldn't figure out how to i...

...tribute's value is a section offset to the line no > info for current compilation unit. If there is only one  compilation > unit generated per .o file then it is always zero. What kind of errors > are you seeing ? > > - > Devang > > On Tue, Jun 29, 2010 at 9:02 AM, Artur Pietrek <pietreka at gmail.com> wrote: >> Hi all, >> While implementing debug info for our backend, we've noticed a problem with >> debug_line section. We believe that the following code is wrong: >> // DW_AT_stmt_list is a offset of line number information for this >&g...

Hi All, Since few days I observe weird change. Consider the following C code char array[] = "0123456789"; extern int test(char arr[], int size); int main(void) { return test(array-1, sizeof(array)-1); } using clang frontend i get this: %call = call i32 @test(i8* getelementptr inbounds ([11 x i8]* @array, i32 0, i32 -1), i32 10) ; <i32> [#uses=1] and using LLVM-GCC this: %1 =

Hi Andrew, thanks for answering On Thu, Apr 15, 2010 at 3:35 PM, Andrew Lenharth <andrewl at lenharth.org>wrote: > On Thu, Apr 15, 2010 at 3:40 AM, Artur Pietrek <pietreka at gmail.com> wrote: > > Hi all > > Ups, I'm really sorry for that previous message, I've sent it by mistake. > > > > So let me write it once more. > > > > I've been working for some time now on a backend for our CPU. However I > &g...

Hi Artur, Artur Pietrek wrote: > Hello, > > I work in Kalray (Montbonnot, France) and I'm PhD student at Universite > Joseph Fourier in Grenoble. > We want to use LLVM framework for MSIL code generation, which is part of > my thesis. > Currently I'm still reading LLVM's documentation and...

On Fri, Aug 21, 2009 at 2:02 AM, Artur Pietrek<pietreka at gmail.com> wrote: > Hi All, > Since few days I observe weird change. > Consider the following C code > > char array[] = "0123456789"; > extern int test(char arr[], int size); > > int main(void) { >   return test(array-1, sizeof(array)-1); >...

Hi Artur, The Thumb2 target (in lib/Targets/ARM/ARMInstrThumb2.td) materializes a 32-bit constant by a two-instruction sequence to load the low and high half-words. It's not pretty, but it works. The pattern is at the bottom of the file. Regards, -Jim On Oct 6, 2009, at 5:10 AM, Artur Pietrek wrote: > Hi all, > I'm working on my own backend for a custom CPU. I have defined > paired registers for 64bit operations, however to set a 64bit paired > register with 64bit immediate I have to set each register in that > pair separately with the higher and the lower 32bi...

Le 20 oct. 2009 à 10:27, Artur Pietrek a écrit : > Hi Jean-Daniel > > On Mon, Oct 19, 2009 at 3:24 PM, Jean-Daniel Dupas <devlists at shadowlab.org > > wrote: > > Le 19 oct. 2009 à 15:05, Kenneth Uildriks a écrit : > FWIW, there is a LLVM bar camp planed in Paris the next month: > > http://barcamp.org/...

DW_AT_stmt_list attribute's value is a section offset to the line no info for current compilation unit. If there is only one compilation unit generated per .o file then it is always zero. What kind of errors are you seeing ? - Devang On Tue, Jun 29, 2010 at 9:02 AM, Artur Pietrek <pietreka at gmail.com> wrote: > Hi all, > While implementing debug info for our backend, we've noticed a problem with > debug_line section. We believe that the following code is wrong: > // DW_AT_stmt_list is a offset of line number information for this > // compile unit i...

...to the line no > > info for current compilation unit. If there is only one compilation > > unit generated per .o file then it is always zero. What kind of errors > > are you seeing ? > > > > - > > Devang > > > > On Tue, Jun 29, 2010 at 9:02 AM, Artur Pietrek <pietreka at gmail.com> > wrote: > >> Hi all, > >> While implementing debug info for our backend, we've noticed a problem > with > >> debug_line section. We believe that the following code is wrong: > >> // DW_AT_stmt_list is a offset of line numb...

Hi Jean-Daniel On Mon, Oct 19, 2009 at 3:24 PM, Jean-Daniel Dupas <devlists at shadowlab.org>wrote: > > Le 19 oct. 2009 à 15:05, Kenneth Uildriks a écrit : > FWIW, there is a LLVM bar camp planed in Paris the next month: > > http://barcamp.org/LLVM%20BarCamp%20Paris (French web page) > > > -- Jean-Daniel > Could you please tell me if it will be in French or

On Wed, Jun 30, 2010 at 1:57 AM, Artur Pietrek <pietreka at gmail.com> wrote: > Hi Devang, > Thanks for working on that. Unfortunately after your change it still doesn't > work (I've tried x86 and our backend under Linux). What errors exactly you are seeing ? > The problem is that you put difference between two label...

Hi all, While implementing debug info for our backend, we've noticed a problem with debug_line section. We believe that the following code is wrong: // DW_AT_stmt_list is a offset of line number information for this // compile unit in debug_line section. It is always zero when only one // compile unit is emitted in one object file. addUInt(Die, dwarf::DW_AT_stmt_list, dwarf::DW_FORM_data4,

Hi all,I'm working on my own backend for a custom CPU. I have defined paired registers for 64bit operations, however to set a 64bit paired register with 64bit immediate I have to set each register in that pair separately with the higher and the lower 32bits of the immediate. Could anyone give me an advice how to describe it in *InstructionInfo.td or point me to something similar in the LLVM

Hi,Could someone explain to me how the sign/zero extensions in LLVM work, please? If I understood correctly, the int type in LLVM doesn't keep the information about signedness of an int. So the question is how can I know if instructions like Load or Trunc should be signed or not? I guess that at least ARM backend produces sign extended load so if someone could point me to the code where it

Hi, So for everybody who could be interested in LLVM Camp in Paris - it will be in French. I've just received an email from Eric Mahé. Artur On Tue, Oct 20, 2009 at 10:36 AM, Jean-Daniel Dupas <devlists at shadowlab.org>wrote: > > Le 20 oct. 2009 à 10:27, Artur Pietrek a écrit : > > Hi Jean-Daniel >> >> On Mon, Oct 19, 2009 at 3:24 PM, Jean-Daniel Dupas < >> devlists at shadowlab.org> wrote: >> >> Le 19 oct. 2009 à 15:05, Kenneth Uildriks a écrit : >> FWIW, there is a LLVM bar camp planed in Paris the next month: &...

Hi all, while I was playing a little bit with IRBuilder I ended up with something like this when included NoFolder.h /work/llvm/include/llvm/User.h: In member function ‘llvm::Value* llvm::NoFolder::CreateExtractElement(llvm::Constant*, llvm::Constant*) const’: /work/llvm/include/llvm/User.h:48: error: ‘static void* llvm::User::operator new(size_t)’ is private