Displaying 10 results from an estimated 10 matches for "40048b".
Did you mean:
40048c
2016 May 30
0
[cfe-dev] How to debug if LTO generate wrong code?
...LTO. Since modern system widely use the 64bit, the code need to run in high address (larger than 2 GB) is a reasonable requirement.
$ gcc -g -O0 -flto codemodel1.c -mcmodel=large -o codemodel1_large_lto_gcc.bin
$ objdump -dS codemodel1_large_lto_gcc.bin
int main(int argc, const char* argv[])
{
40048b: 55 push %rbp
40048c: 48 89 e5 mov %rsp,%rbp
40048f: 48 83 ec 20 sub $0x20,%rsp
400493: 89 7d ec mov %edi,-0x14(%rbp)
400496: 48 89 75 e0 mov %rsi,-0x20(%rbp)
int t = g...
2016 May 30
2
[cfe-dev] How to debug if LTO generate wrong code?
...ion to add.
What is the linker you're using? Are you building your own clang?
--
Mehdi
>
> $ gcc -g -O0 -flto codemodel1.c -mcmodel=large -o codemodel1_large_lto_gcc.bin
> $ objdump -dS codemodel1_large_lto_gcc.bin
>
> int main(int argc, const char* argv[])
> {
> 40048b: 55 push %rbp
> 40048c: 48 89 e5 mov %rsp,%rbp
> 40048f: 48 83 ec 20 sub $0x20,%rsp
> 400493: 89 7d ec mov %edi,-0x14(%rbp)
> 400496: 48 89 75 e0 mov %rsi,-0x20...
2016 May 30
0
[cfe-dev] How to debug if LTO generate wrong code?
...you're using? Are you building your own clang?
>
> --
> Mehdi
>
>
>
>
>
> $ gcc -g -O0 -flto codemodel1.c -mcmodel=large -o
> codemodel1_large_lto_gcc.bin
> $ objdump -dS codemodel1_large_lto_gcc.bin
>
> int main(int argc, const char* argv[])
> {
> 40048b: 55 push %rbp
> 40048c: 48 89 e5 mov %rsp,%rbp
> 40048f: 48 83 ec 20 sub $0x20,%rsp
> 400493: 89 7d ec mov %edi,-0x14(%rbp)
> 400496: 48 89 75 e0 mov %rsi,-0x20...
2016 May 30
0
[cfe-dev] How to debug if LTO generate wrong code?
...ering that it is really a trivial option to add.
What is the linker you're using? Are you building your own clang?
--
Mehdi
$ gcc -g -O0 -flto codemodel1.c -mcmodel=large -o codemodel1_large_lto_gcc.bin
$ objdump -dS codemodel1_large_lto_gcc.bin
int main(int argc, const char* argv[])
{
40048b: 55 push %rbp
40048c: 48 89 e5 mov %rsp,%rbp
40048f: 48 83 ec 20 sub $0x20,%rsp
400493: 89 7d ec mov %edi,-0x14(%rbp)
400496: 48 89 75 e0 mov %rsi,-0x20(%rbp)
int t = g...
2016 May 30
7
[cfe-dev] How to debug if LTO generate wrong code?
...re using? Are you building your own clang?
>
> --
> Mehdi
>
>
>
>
>
> $ gcc -g -O0 -flto codemodel1.c -mcmodel=large -o codemodel1_large_lto_gcc.bin
> $ objdump -dS codemodel1_large_lto_gcc.bin
>
> int main(int argc, const char* argv[])
> {
> 40048b: 55 push %rbp
> 40048c: 48 89 e5 mov %rsp,%rbp
> 40048f: 48 83 ec 20 sub $0x20,%rsp
> 400493: 89 7d ec mov %edi,-0x14(%rbp)
> 400496: 48 89 75 e0 mov %rsi,-0x20...
2016 May 30
0
[cfe-dev] How to debug if LTO generate wrong code?
...dering that it is really a trivial option to add.
What is the linker you're using? Are you building your own clang?
--
Mehdi
$ gcc -g -O0 -flto codemodel1.c -mcmodel=large -o codemodel1_large_lto_gcc.bin
$ objdump -dS codemodel1_large_lto_gcc.bin
int main(int argc, const char* argv[])
{
40048b: 55 push %rbp
40048c: 48 89 e5 mov %rsp,%rbp
40048f: 48 83 ec 20 sub $0x20,%rsp
400493: 89 7d ec mov %edi,-0x14(%rbp)
400496: 48 89 75 e0 mov %rsi,-0x20(%rbp)
int t = g...
2016 May 29
4
[cfe-dev] How to debug if LTO generate wrong code?
Hi,
> On May 29, 2016, at 7:36 AM, Shi, Steven <steven.shi at intel.com> wrote:
>
> Hi Mehdi,
> After deeper debug, I found my firmware LTO wrong code issue is related to X64 code model (-mcmodel=large) is always overridden as small (-mcmodel=small) if LTO build. And I don't know how to correctly specific the large code model for my X64 firmware LTO build. Appreciate if
2016 May 30
1
[cfe-dev] How to debug if LTO generate wrong code?
...> > Mehdi
> >
> >
> >
> >
> >
> > $ gcc -g -O0 -flto codemodel1.c -mcmodel=large -o
> > codemodel1_large_lto_gcc.bin
> > $ objdump -dS codemodel1_large_lto_gcc.bin
> >
> > int main(int argc, const char* argv[])
> > {
> > 40048b: 55 push %rbp
> > 40048c: 48 89 e5 mov %rsp,%rbp
> > 40048f: 48 83 ec 20 sub $0x20,%rsp
> > 400493: 89 7d ec mov %edi,-0x14(%rbp)
> > 400496: 48 89 75 e0 mov %rsi,-0x20(%rbp)
> > int t = global_func(argc);
> > 40049a: 8b 45 ec mov -0x14(%rbp),%eax
> > 40049...
2016 May 30
2
[cfe-dev] How to debug if LTO generate wrong code?
...e using? Are you building your own clang?
>
> --
> Mehdi
>
>
>
>
>
> $ gcc -g -O0 -flto codemodel1.c -mcmodel=large -o codemodel1_large_lto_gcc.bin
> $ objdump -dS codemodel1_large_lto_gcc.bin
>
> int main(int argc, const char* argv[])
> {
> 40048b: 55 push %rbp
> 40048c: 48 89 e5 mov %rsp,%rbp
> 40048f: 48 83 ec 20 sub $0x20,%rsp
> 400493: 89 7d ec mov %edi,-0x14(%rbp)
> 400496: 48 89 75 e0 mov %rsi,-0x20...
2016 May 30
0
[cfe-dev] How to debug if LTO generate wrong code?
...dering that it is really a trivial option to add.
What is the linker you're using? Are you building your own clang?
--
Mehdi
$ gcc -g -O0 -flto codemodel1.c -mcmodel=large -o codemodel1_large_lto_gcc.bin
$ objdump -dS codemodel1_large_lto_gcc.bin
int main(int argc, const char* argv[])
{
40048b: 55 push %rbp
40048c: 48 89 e5 mov %rsp,%rbp
40048f: 48 83 ec 20 sub $0x20,%rsp
400493: 89 7d ec mov %edi,-0x14(%rbp)
400496: 48 89 75 e0 mov %rsi,-0x20(%rbp)
int t = g...