search for: kbuild_str

...Wall -Wstrict-prototypes -march=i386 -mregparm=3 -include /home/sclark/rpmbuild/BUILD/kernel-2.6.32/arch/x86/kernel/acpi/realmode/../../../boot/code16gcc.h -fno-strict-aliasing -fomit-frame-pointer -ffreestanding -fno-toplevel-reorder -fno-stack-protector -mpreferred-stack-boundary=2 -m32 -D"KBUILD_STR(s)=#s" -D"KBUILD_BASENAME=KBUILD_STR(wakemain)" -D"KBUILD_MODNAME=KBUILD_STR(wakemain)" -D"DEBUG_HASH=57" -D"DEBUG_HASH2=38" -c -o arch/x86/kernel/acpi/realmode/.tmp_wakemain.o arch/x86/kernel/acpi/realmode/wakemain.c cc1: warnings being treated as err...

...> or local variables). > > What is the difference between your test case and application ? Is your application compiled using same compiler options ? My application is the linux kernel TCP/IP stack layer. There are few #defines and compiler options which are different. Such as -D"KBUILD_STR(s)=#s" -D"KBUILD_MODNAME=KBUILD_STR()" -D__KERNEL__, -fno-common -fno-strict-aliasing. Are these options in any way responsible for the problems I am facing while debugging. At this moment it is not possible for me to run my application standalone without modifying it. Thanks for...

...and/ulp/ipoib -I/root/lustre/ 1.6.4.2/ofa_kernel-1.2/drivers/infiniband/debug -I/root/lustre/ 1.6.4.2/ofa_kernel-1.2/drivers/infiniband/hw/cxgb3/core -I/root/ lustre/1.6.4.2/ofa_kernel-1.2/drivers/net/cxgb3 -I/root/lustre/ 1.6.4.2/ofa_kernel-1.2/drivers/net/rds -DMODULE -D"KBUILD_STR(s) =#s" -D"KBUILD_BASENAME=KBUILD_STR(ipoib_fs)" - D"KBUILD_MODNAME=KBUILD_STR(ib_ipoib)" -c -o /root/lustre/1.6.4.2/ ofa_kernel-1.2/drivers/infiniband/ulp/ipoib/.tmp_ipoib_fs.o /root/ lustre/1.6.4.2/ofa_kernel-1.2/drivers/infiniband/ulp/ipoib/ipoib_fs.c /root/lustre/1...

...ion -O2 -mtune=generic -m64 -mno-red-zone -mcmodel=kernel -pipe -Wno-sign-compare -fno-asynchronous-unwind-tables -funit-at-a-time -mno-sse -mno-mmx -mno-sse2 -mno-3dnow -maccumulate-outgoing-args -fomit-frame-pointer -g -fno-stack-protector -Wdeclaration-after-statement -Wno-pointer-sign -D"KBUILD_STR(s)=#s" -D"KBUILD_BASENAME=KBUILD_STR(syscall)" -D"KBUILD_MODNAME=KBUILD_STR(syscall)" -c -o arch/x86_64/kernel/.tmp_syscall.o arch/x86_64/kernel/syscall.c arch/x86_64/kernel/syscall.c:22: error: '__NR_syscall_max' undeclared here (not in a function) arch/x86_64/kern...

...-emit-llvm" /bin/bash scripts/checksyscalls.sh llvm-gcc -Wp,-MD,./.missing-syscalls.d -nostdinc -isystem /home/ashish/llvm/llvm-gcc4.2-2.3.source/obj/../install/lib/gcc/x86_64-unknown-linux-gnu/4.2.1/include -D__KERNEL__ -Iinclude -include include/linux/autoconf.h -O2 -emit-llvm -D"KBUILD_STR(s)=#s" -D"KBUILD_BASENAME=KBUILD_STR(missing_syscalls)" -D"KBUILD_MODNAME=KBUILD_STR(missing_syscalls)" make -f scripts/Makefile.build obj=scripts make -f scripts/Makefile.build obj=scripts/genksyms make -f scripts/Makefile.build obj=scripts/mod scripts/mod/mk_elfconfig x...

...gt;> >> What is the difference between your test case and application ? Is your application compiled using same compiler options ? > > My application is the linux kernel TCP/IP stack layer. There are > few #defines and compiler options which are different. Such as > -D"KBUILD_STR(s)=#s" -D"KBUILD_MODNAME=KBUILD_STR()" -D__KERNEL__, > -fno-common -fno-strict-aliasing. > > Are these options in any way responsible for the problems I am facing > while debugging. I do not see anything obvious here. - Devang > At this moment it is not possible fo...

...m64 -mno-red-zone -mcmodel=kernel -pipe -Wno-sign-compare > -fno-asynchronous-unwind-tables -funit-at-a-time -mno-sse -mno-mmx > -mno-sse2 -mno-3dnow -maccumulate-outgoing-args > -fomit-frame-pointer -g -fno-stack-protector > -Wdeclaration-after-statement -Wno-pointer-sign > -D"KBUILD_STR(s)=#s" -D"KBUILD_BASENAME=KBUILD_STR(syscall)" > -D"KBUILD_MODNAME=KBUILD_STR(syscall)" -c -o > arch/x86_64/kernel/.tmp_syscall.o arch/x86_64/kernel/syscall.c > arch/x86_64/kernel/syscall.c:22: error: '__NR_syscall_max' undeclared > here (not in a functi...

...-DCONFIG_AS_CFI=1 -DCONFIG_AS_CFI_SIGNAL_FRAME=1 -pipe -Wno-sign-compare -fno-asynchronous-unwind-tables -mno-sse -mno-mmx -mno-sse2 -mno-3dnow -fno-stack-protector -fno-omit-frame-pointer -fno-optimize-sibling-calls -pg -Wdeclaration-after-statement -Wno-pointer-sign -fno-strict-overflow -D"KBUILD_STR(s)=#s" -D"KBUILD_BASENAME=KBUILD_STR(main)" -D"KBUILD_MODNAME=KBUILD_STR(main)" -c -o init/.tmp_main.o init/main.c UNREACHABLE executed! init/main.c:908: internal compiler error: Aborted Please submit a full bug report, with preprocessed source if appropriate. See <URL:...

On Fri, Sep 26, 2008 at 9:19 PM, Ashish Bijlani <ashish.bijlani at gmail.com> wrote: > Hi, > > I'm trying to compile linux-2.6.23.16 with llvm-2.3. Is it at all > possible? Yes, but it requires significant hacking, and the result for 2.6 is a mostly bitcode kernel with a few userspace shared libraries linked in as objcode (yes, the kernel builds .so files and includes them

In your example, you do not need to update debug info for @global_var at the moment. We are not identifying tls in debug info yet. On Oct 13, 2010, at 8:30 AM, shankha wrote: > I do not face any issues debugging my test case. But while debugging > my application > through gdb I cannot make sense of the call stack. I do not see the > function names in > the call stack (with or

...s). > > What is the difference between your test case and application ? Is your > application compiled using same compiler options ? > >   My application is the linux kernel TCP/IP stack layer. There are > few #defines and compiler options which are different. Such as > -D"KBUILD_STR(s)=#s" -D"KBUILD_MODNAME=KBUILD_STR()" -D__KERNEL__, > -fno-common -fno-strict-aliasing. > > Are these options in any way responsible for the problems I am facing > while debugging. > > I do not see anything obvious here. > - > Devang > > At this moment...

...cmodel=kernel -pipe -Wno-sign-compare >> -fno-asynchronous-unwind-tables -funit-at-a-time -mno-sse -mno-mmx >> -mno-sse2 -mno-3dnow -maccumulate-outgoing-args >> -fomit-frame-pointer -g -fno-stack-protector >> -Wdeclaration-after-statement -Wno-pointer-sign >> -D"KBUILD_STR(s)=#s" -D"KBUILD_BASENAME=KBUILD_STR(syscall)" >> -D"KBUILD_MODNAME=KBUILD_STR(syscall)" -c -o >> arch/x86_64/kernel/.tmp_syscall.o arch/x86_64/kernel/syscall.c >> arch/x86_64/kernel/syscall.c:22: error: '__NR_syscall_max' undeclared >> here...

Hi Devang, I convert all global variables in a file to thread local at the IR level. i.e. compile example_llvm.c to IR example_llvm.ll and change global variables to thread-local variables. I also insert a function call just before access of the global(now thread-local) variable. I also insert a local variable in main. Does these operations in any way effect the debug metadata ? I do not face

Hi everyone, If there any modules (drivers) for Video Graphic Accelerated Card nVIDIA GeForce 8400 G in Xen? Cause the driver that I downloaded from nvidia.com won´t work with Xen Kernel. Any Idea? I use CentOS 5.1 I appreciate your helps very much thank you Eric Jansen _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com