Hi Reid, I'll write a separate post about the intrinsics, but just a quick note about the CFLAGS issue. Reid Spencer kirjoitti:> On Thu, 2006-11-09 at 15:29 +0200, Pertti Kellomäki wrote: >> Another related thing is that even when I defined -emit-llvm in >> what I thought would be a global CFLAGS for all of newlib, it did >> not get propagated to all subdirectories.>> Oh? Which ones did it not get propagated to?I did not see it being propagated to libgloss, but maybe I was trying to define the flags at the wrong place. Since the llvm-gcc shell script solved my immediate problem, I did not bother looking any further. -- Pertti
Hi Pertti, On Thu, 2006-11-09 at 18:41 +0200, Pertti Kellomäki wrote:> Hi Reid, > > I'll write a separate post about the intrinsics, but just > a quick note about the CFLAGS issue.Okay.> > Reid Spencer kirjoitti: > > On Thu, 2006-11-09 at 15:29 +0200, Pertti Kellomäki wrote: > >> Another related thing is that even when I defined -emit-llvm in > >> what I thought would be a global CFLAGS for all of newlib, it did > >> not get propagated to all subdirectories. > > > > Oh? Which ones did it not get propagated to? > > I did not see it being propagated to libgloss, but maybe I > was trying to define the flags at the wrong place. Since the > llvm-gcc shell script solved my immediate problem, I did not > bother looking any further.I don't think I understand the problem properly. I thought you were claiming that CFLAGS was not being passed down through the llvm-gcc directories properly as llvm-gcc was built. However, llvm-gcc doesn't have a libgloss. So, now I'm not sure what you're talking about. Is libgloss part of newlib? If so, please note that it is not llvm-gcc's job to pass CFLAGS down. That would be a bug in the newlib makefiles. :) Reid.
Reid Spencer kirjoitti:> So, now I'm not sure what you're talking about. Is > libgloss part of newlib? If so, please note that it is not llvm-gcc's > job to pass CFLAGS down. That would be a bug in the newlib makefiles. :)Sorry for being obtuse. Yes, if there indeed is a bug, it is in the newlib build system. I was trying to compile newlib with llvm-gcc. The need for propagating compiler flags arises because if I want to create newlib libraries that contain LLVM byte code rather than host object files, I need to pass -emit-llvm to all invocations of llvm-gcc. Hope this clarifies a bit. -- Pertti