<div dir="ltr">So is for PE32 and PE32+. They cannot be mixed because they are for x86 and x86-64, respectively.<div><br></div><div>I'd think we can simply wait for all files to be parsed and pass them to a LinkingContext to ask whether or not the input file set seems OK.</div>
</div><div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, Apr 1, 2014 at 9:59 PM, Shankar Easwaran <span dir="ltr"><<a href="mailto:shankare@codeaurora.org" target="_blank">shankare@codeaurora.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="HOEnZb"><div class="h5">On 4/1/2014 11:51 PM, Simon Atanasyan wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
On Wed, Apr 2, 2014 at 7:47 AM, Shankar Easwaran<br>
<<a href="mailto:shankare@codeaurora.org" target="_blank">shankare@codeaurora.org</a>> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I am not sure if you looked at this thread<br>
(<a href="http://lists.cs.uiuc.edu/pipermail/llvmdev/2013-October/066155.html" target="_blank">http://lists.cs.uiuc.edu/<u></u>pipermail/llvmdev/2013-<u></u>October/066155.html</a>)<br>
<br>
let me know if you still have questions.<br>
<br>
As a short summary, we dont verify the architecture of files that are being<br>
read. We could very well be passed in a hexagon input file while the target<br>
specified was x86_64. we got to reject the input file as the user has chosen<br>
the architecture to be x86_64.<br>
</blockquote>
Moreover, inside MIPS architecture there are some incompatible<br>
"sub-architectures". It would be nice if we can check input files and<br>
reject incorrect combinations.<br>
</blockquote></div></div>
For a simple design, I was thinking that the LinkingContext per flavor could store input file information as its processed by the linker and choose to reject files or accept them.<br>
<br>
The only problem here is that since the input files are parsed in parallel, how do we want to deal with this scenario ?<div class="HOEnZb"><div class="h5"><br>
<br>
Thanks<br>
<br>
Shankar Easwaran<br>
<br>
-- <br>
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, hosted by the Linux Foundation<br>
<br>
</div></div></blockquote></div><br></div>