This is the mail archive of the
gcc-help@gcc.gnu.org
mailing list for the GCC project.
Re: what's the right way to use custom entry point
- From: Florian Weimer <fw at deneb dot enyo dot de>
- To: Cong Monkey <congzhangzh at gmail dot com>
- Cc: gcc-help at gcc dot gnu dot org
- Date: Sun, 06 Nov 2016 14:07:16 +0100
- Subject: Re: what's the right way to use custom entry point
- Authentication-results: sourceware.org; auth=none
- References: <CAOXDmPrEA1hEaP35Cu29LtzVHMPqBqveGj8E5cowZgngqBWxSA@mail.gmail.com> <8737jk42d8.fsf@mid.deneb.enyo.de> <CAOXDmPpeFqwV6UJTgsV2bJU3RW50aWdvJZo7H0v7PCh5Q1tEUQ@mail.gmail.com> <87shr4lriq.fsf@mid.deneb.enyo.de> <CAOXDmPoT0k9Q3Nnu0ecMs3yhNzbne=RCnua=fT1A064iEvWrEg@mail.gmail.com>
* Cong Monkey:
>> The easiest way is to link against an existing libc, or at least its
>> startup code.
>
> If I use custom entry point, the argc and argv I get is very strange,
> it's not the same as I get from normally main entry point!
That's expected. You have to implement your own startup code. It's
the reason why linking against an existing libc is the easiest
solution.