On Tue, Feb 2, 2016 at 4:23 PM, David Edelsohn wrote:
> On Tue, Feb 2, 2016 at 5:03 PM, H.J. Lu wrote:
>> On Tue, Feb 2, 2016 at 1:35 PM, Cary Coutant wrote:
include/plugin-api.h defines an ABI between linker and compiler,
which can be used to implement linker plug-in by any compilers.
On Tue, Feb 2, 2016 at 4:23 PM, David Edelsohn wrote:
> On Tue, Feb 2, 2016 at 5:03 PM, H.J. Lu wrote:
>> On Tue, Feb 2, 2016 at 1:35 PM, Cary Coutant wrote:
include/plugin-api.h defines an ABI between linker and compiler,
which can be used to implement linker plug-in by any compilers.
On Tue, Feb 2, 2016 at 5:03 PM, H.J. Lu wrote:
> On Tue, Feb 2, 2016 at 1:35 PM, Cary Coutant wrote:
>>> include/plugin-api.h defines an ABI between linker and compiler,
>>> which can be used to implement linker plug-in by any compilers.
>>> I'd like to add GCC Runtime Library Exception to includ
On 22.01.2016 08:27, Matthias Klose wrote:
On 22.01.2016 06:09, Martin Michlmayr wrote:
In terms of build failures, I reported 520 bugs to Debian. Most of them
were new GCC errors or warnings (some packages use -Werror and many
-Werror=format-security).
Here are some of the most frequent error
Snapshot gcc-5-20160202 is now available on
ftp://gcc.gnu.org/pub/gcc/snapshots/5-20160202/
and on various mirrors, see http://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 5 SVN branch
with the following options: svn://gcc.gnu.org/svn/gcc/branches/gcc-5
On Tue, Feb 2, 2016 at 1:35 PM, Cary Coutant wrote:
>> include/plugin-api.h defines an ABI between linker and compiler,
>> which can be used to implement linker plug-in by any compilers.
>> I'd like to add GCC Runtime Library Exception to include/plugin-api.h
>> so that the linker plug-in can have
> include/plugin-api.h defines an ABI between linker and compiler,
> which can be used to implement linker plug-in by any compilers.
> I'd like to add GCC Runtime Library Exception to include/plugin-api.h
> so that the linker plug-in can have non-GPL licenses.
This is OK with me.
-cary
On 02/02/2016 05:41 PM, Manuel López-Ibáñez wrote:
> Everything is possible! Not sure how hard it would be, though. As
> said, GJC, the Java FE, was doing something similar sometime ago, but
> it has perhaps bit-rotted now.
It is doing something the other way around: bytecode to Gimple.
Andrew.
On 1 February 2016 at 22:21, Bertram, Alexander wrote:
> I'm not sure exactly where it would fit in however- I don't think it
> could be described with the machine description language. There is
> alot of complexity involved in handling things like addressable local
> variables, which have to be a
On Mon, Feb 1, 2016 at 7:45 PM, Jeff Law wrote:
> On 02/01/2016 12:07 PM, Bin.Cheng wrote:
>>
>> On Mon, Feb 1, 2016 at 6:08 PM, Andreas Schwab
>> wrote:
>>>
>>> "Bin.Cheng" writes:
>>>
Seems to me Andrew was right in comment of PR69559, that we simply
couldn't bootstrap GCC with sysro
On 02/01/2016 11:21 PM, Bertram, Alexander wrote:
> Would it be possible to write a
> backend that generates code from Gimple and not RTL?
Hi.
Actually, HSA back-end is such an example. Where we directly emit HSAIL code
in form of BRIG (binary representation of the textual representation of HSAIL
11 matches
Mail list logo
