Re: [PATCH 2/4] x86: Move instruction decoder data into header

2014-04-15 Thread Masami Hiramatsu
(2014/04/15 23:24), Sasha Levin wrote: > On 04/14/2014 11:10 PM, Masami Hiramatsu wrote: >> (2014/04/15 11:28), Sasha Levin wrote: >>> On 04/14/2014 09:41 PM, Masami Hiramatsu wrote: (2014/04/15 2:44), Sasha Levin wrote: >> Right now we generate data for the instruction decoder and place

Re: [PATCH 2/4] x86: Move instruction decoder data into header

2014-04-15 Thread Sasha Levin
On 04/14/2014 11:10 PM, Masami Hiramatsu wrote: > (2014/04/15 11:28), Sasha Levin wrote: >> On 04/14/2014 09:41 PM, Masami Hiramatsu wrote: >>> (2014/04/15 2:44), Sasha Levin wrote: > Right now we generate data for the instruction decoder and place it > as a code file which gets #included

Re: [PATCH 2/4] x86: Move instruction decoder data into header

2014-04-15 Thread Sasha Levin
On 04/14/2014 11:10 PM, Masami Hiramatsu wrote: (2014/04/15 11:28), Sasha Levin wrote: On 04/14/2014 09:41 PM, Masami Hiramatsu wrote: (2014/04/15 2:44), Sasha Levin wrote: Right now we generate data for the instruction decoder and place it as a code file which gets #included directly (yuck).

Re: [PATCH 2/4] x86: Move instruction decoder data into header

2014-04-15 Thread Masami Hiramatsu
(2014/04/15 23:24), Sasha Levin wrote: On 04/14/2014 11:10 PM, Masami Hiramatsu wrote: (2014/04/15 11:28), Sasha Levin wrote: On 04/14/2014 09:41 PM, Masami Hiramatsu wrote: (2014/04/15 2:44), Sasha Levin wrote: Right now we generate data for the instruction decoder and place it as a code

Re: Re: [PATCH 2/4] x86: Move instruction decoder data into header

2014-04-14 Thread Masami Hiramatsu
(2014/04/15 11:28), Sasha Levin wrote: > On 04/14/2014 09:41 PM, Masami Hiramatsu wrote: >> (2014/04/15 2:44), Sasha Levin wrote: Right now we generate data for the instruction decoder and place it as a code file which gets #included directly (yuck). Instead, make it a header

Re: [PATCH 2/4] x86: Move instruction decoder data into header

2014-04-14 Thread Sasha Levin
On 04/14/2014 09:41 PM, Masami Hiramatsu wrote: > (2014/04/15 2:44), Sasha Levin wrote: >> > Right now we generate data for the instruction decoder and place it >> > as a code file which gets #included directly (yuck). >> > >> > Instead, make it a header which will also be usable by other code >>

Re: [PATCH 2/4] x86: Move instruction decoder data into header

2014-04-14 Thread Masami Hiramatsu
(2014/04/15 2:44), Sasha Levin wrote: > Right now we generate data for the instruction decoder and place it > as a code file which gets #included directly (yuck). > > Instead, make it a header which will also be usable by other code > that wants to use the data in there. Hmm, making the

Re: [PATCH 2/4] x86: Move instruction decoder data into header

2014-04-14 Thread Masami Hiramatsu
(2014/04/15 2:44), Sasha Levin wrote: Right now we generate data for the instruction decoder and place it as a code file which gets #included directly (yuck). Instead, make it a header which will also be usable by other code that wants to use the data in there. Hmm, making the generated

Re: [PATCH 2/4] x86: Move instruction decoder data into header

2014-04-14 Thread Sasha Levin
On 04/14/2014 09:41 PM, Masami Hiramatsu wrote: (2014/04/15 2:44), Sasha Levin wrote: Right now we generate data for the instruction decoder and place it as a code file which gets #included directly (yuck). Instead, make it a header which will also be usable by other code that wants to

Re: Re: [PATCH 2/4] x86: Move instruction decoder data into header

2014-04-14 Thread Masami Hiramatsu
(2014/04/15 11:28), Sasha Levin wrote: On 04/14/2014 09:41 PM, Masami Hiramatsu wrote: (2014/04/15 2:44), Sasha Levin wrote: Right now we generate data for the instruction decoder and place it as a code file which gets #included directly (yuck). Instead, make it a header which will also be