Re: [PATCH v4 01/20] softmmu: split off vl.c:main() into main.c

2019-11-12 Thread Alexander Bulekov
On 11/5/19 11:41 AM, Darren Kenny wrote: On Wed, Oct 30, 2019 at 02:49:48PM +, Oleinik, Alexander wrote: From: Alexander Oleinik A program might rely on functions implemented in vl.c, but implement its own main(). By placing main into a separate source file, there are no complaints about

Re: [PATCH v4 01/20] softmmu: split off vl.c:main() into main.c

2019-11-06 Thread Stefan Hajnoczi
On Wed, Oct 30, 2019 at 02:49:48PM +, Oleinik, Alexander wrote: > diff --git a/main.c b/main.c > new file mode 100644 > index 00..ecd6389424 > --- /dev/null > +++ b/main.c > @@ -0,0 +1,52 @@ > +/* > + * QEMU System Emulator > + * > + * Copyright (c) 2003-2008 Fabrice Bellard > + * > +

Re: [PATCH v4 01/20] softmmu: split off vl.c:main() into main.c

2019-11-05 Thread Darren Kenny
On Wed, Oct 30, 2019 at 02:49:48PM +, Oleinik, Alexander wrote: From: Alexander Oleinik A program might rely on functions implemented in vl.c, but implement its own main(). By placing main into a separate source file, there are no complaints about duplicate main()s when linking against

[PATCH v4 01/20] softmmu: split off vl.c:main() into main.c

2019-10-30 Thread Oleinik, Alexander
From: Alexander Oleinik A program might rely on functions implemented in vl.c, but implement its own main(). By placing main into a separate source file, there are no complaints about duplicate main()s when linking against vl.o. For example, the virtual-device fuzzer uses a main() provided by