Re: Ad-hoc notes from the "pending patches" BOF at the GNU tools cauldron.

On Tue, 10 Jul 2012, Dimitrios Apostolou wrote: * Have a field in the bugzilla keeping "related ML threads" URLs. What I do now is post a separate comment saying "discussed here" or "posted patch here". Not sure if good enough, but on bugs I've not seen it in cases I needed to. Replying to m

GCC Cauldron: Notes from the C++ ABI BOF

string & list changes - function w/ string arg - classes w/ string members - global variables - link c++98 & c++0x together - link existing c++98 .o & new c++-x .o - link at runtime c++98 .so & new c++0x .so HP: attribute on type propagates to: - function (params or return type) - structs w/ mem

Change default BOOT_CFLAGS for release builds

Hello list, we discussed the subject in the BOF but I didn't quite get what the consensus is, so that I can start changing things. What I have in mind is to introduce and document a new "make release" target that builds GCC in the fastest /stable/ way possible, for example --enable-checking=

Re: GCC Cauldron: Notes from the C++ ABI BOF

My version of Cary's notes (I just wrote this on my Google+ stream): We had a useful discussion about C++11 ABI issues at the GNU Tools Cauldron (http://gcc.gnu.org/wiki/cauldron2012). The approach will be shaped over time, but the general idea is as follows. We will modify g++ to support a type

Re: Ad-hoc notes from the "pending patches" BOF at the GNU tools cauldron.

On Mon, Jul 9, 2012 at 4:35 PM, Hans-Peter Nilsson wrote: > On a whim I hosted a BOF at the GNU tools cauldron yesterday, > titled "pending patches" (no compliance with RFC5434 intended). Thanks for the notes. I want to add one point. There are a number of useful tools that we can imagine. How

Re: GCC Cauldron: Notes from the C++ ABI BOF

Hi, On Wed, 11 Jul 2012, Ian Lance Taylor wrote: > We will modify g++ to support a type attribute indicating the version of > the type, as a string. This type attribute will be inherited by any > other type that uses it, as a class/struct member or via inheritance. > Type attributes will be

Re: GCC Cauldron: Notes from the C++ ABI BOF

On Wed, Jul 11, 2012 at 6:18 AM, Ian Lance Taylor wrote: > My version of Cary's notes (I just wrote this on my Google+ stream): > > We had a useful discussion about C++11 ABI issues at the GNU Tools > Cauldron (http://gcc.gnu.org/wiki/cauldron2012). The approach will be > shaped over time, but th

Re: Ad-hoc notes from the "pending patches" BOF at the GNU tools cauldron.

Does anyone have experience with Patchwork? It sounds like it works with a mailing list with less requirement for special markup than dannyb's tracker had. Jason

Re: Ad-hoc notes from the "pending patches" BOF at the GNU tools cauldron.

> From: Dimitrios Apostolou > Date: Tue, 10 Jul 2012 08:25:49 +0200 > Hi hp, thanks for the notes, I'm just going to highlight my point of view. > > Regarding patch pinging, my take is that is should be seldom necessary, > for example I tend to forget my small patches after sometime. Me too, s

Re: problems in interaction between peephole on CALL_INSN and final_scan_insn

On Sun, 8 Jul 2012, Alan Lehotsky wrote: > I'm certain there are better ways; can you be more specific though? > > Or are you just talking about defining a sibcall_epilogue pattern? I'm not Andrew but I think obviously enough "yes". Better to say, perhaps even document, that text peepholes are de

regrename introduces dependencies and causes cprop_hardreg regressions

Hi, I measured the impact of regrename on code size of benchmark CSiBE, using following command line: 1. arm-none-eabi-gcc -mthumb -mcpu=cortex-m0 -Os comparing to 2. arm-none-eabi-gcc -mthumb -mcpu=cortex-m0 -Os -frename-registers And I was surprised that regrename causes many code size regressi