Why some library functions (such as strcpy,strncpy,etc.) are extended in .bc file? How to keep the originally forms of these library functions in .bc file? Thanks - Xia ______________________________________ ע������30��������䣨 http://mail.sina.com.cn/chooseMode.html �� ==================================================================HP����̨ʽ����������ִ���Ͽ��ж� (http://ad4.sina.com.cn/wx/ads/zhuiyu_hprefresh.html)
What do you mean by 'extended', and the 'originally forms'? -Brian> Why some library functions (such as strcpy,strncpy,etc.) are extended > in .bc file? How to keep the originally forms of these library > functions in .bc file?-- gaeke at uiuc.edu
On Tue, 20 Jul 2004, xia_yimin wrote:> Why some library functions (such as strcpy,strncpy,etc.) are extended in .bc file? > How to keep the originally forms of these library functions in .bc file?These come from the library: llvm/runtime/GCCLibraries/libc/ If you don't want them, just go into that directory, delete the functions you don't want, run make clean and make install (in that directory), and they should be gone. -Chris -- http://llvm.cs.uiuc.edu/ http://nondot.org/sabre/
On Tue, 20 Jul 2004, Brian R. Gaeke wrote:> > What do you mean by 'extended', and the 'originally forms'?My interpretation (correct me I'm wrong Xia) is that he wants the calls to strcpy, but we are inlining implementations of some of these library functions at link-time. If this is the case Xia, you can do what I said and take them out of the LLVM libc.bc file, which will prevent inlining from happening. -Chris -- http://llvm.cs.uiuc.edu/ http://nondot.org/sabre/
Apparently Analagous Threads
- [RFC] Propeller: A frame work for Post Link Optimizations
- [RFC] Propeller: A frame work for Post Link Optimizations
- [RFC] Propeller: A frame work for Post Link Optimizations
- [RFC] Propeller: A frame work for Post Link Optimizations
- [RFC] Propeller: A frame work for Post Link Optimizations