> What do you propose that we do?
Probably just jump to 5.0 (or 5.1) without the subsequent acceleration.
> Step 1: We agree that the current major revision number conveys no
> information, and therefore we will change the major revision number
> with every release. (I understand that you do not
On Wed, Aug 06, 2014 at 09:25:48AM +0200, Eric Botcazou wrote:
> > What do you propose that we do?
>
> Probably just jump to 5.0 (or 5.1) without the subsequent acceleration.
That was my preference too.
Jakub
On Wed, Aug 06, 2014 at 09:42:23AM +0200, Jakub Jelinek wrote:
> On Wed, Aug 06, 2014 at 09:25:48AM +0200, Eric Botcazou wrote:
> > > What do you propose that we do?
> >
> > Probably just jump to 5.0 (or 5.1) without the subsequent acceleration.
>
> That was my preference too.
FWIW, me too. Thi
On Wed, Aug 6, 2014 at 9:42 AM, Jakub Jelinek wrote:
> On Wed, Aug 06, 2014 at 09:25:48AM +0200, Eric Botcazou wrote:
>> > What do you propose that we do?
>>
>> Probably just jump to 5.0 (or 5.1) without the subsequent acceleration.
>
> That was my preference too.
What singles out 5.0 to warrant
On Wed, Aug 06, 2014 at 10:44:11AM +0200, Richard Biener wrote:
> On Wed, Aug 6, 2014 at 9:42 AM, Jakub Jelinek wrote:
> > On Wed, Aug 06, 2014 at 09:25:48AM +0200, Eric Botcazou wrote:
> >> > What do you propose that we do?
> >>
> >> Probably just jump to 5.0 (or 5.1) without the subsequent accel
On Wed, Aug 6, 2014 at 10:48 AM, Jakub Jelinek wrote:
> On Wed, Aug 06, 2014 at 10:44:11AM +0200, Richard Biener wrote:
>> On Wed, Aug 6, 2014 at 9:42 AM, Jakub Jelinek wrote:
>> > On Wed, Aug 06, 2014 at 09:25:48AM +0200, Eric Botcazou wrote:
>> >> > What do you propose that we do?
>> >>
>> >> P
On Wed, Aug 06, 2014 at 11:04:14AM +0200, Richard Biener wrote:
> > - libstdc++ ABI changes (it is a significant user visible change,
> > if you rebuild everything, no extra effort is needed, but otherwise
> > if you want some C++ code built with older compilers work together
> > with code bu
On Wed, Aug 06, 2014 at 11:04:14AM +0200, Richard Biener wrote:
> On Wed, Aug 6, 2014 at 10:48 AM, Jakub Jelinek wrote:
> > - libstdc++ ABI changes (it is a significant user visible change,
> > if you rebuild everything, no extra effort is needed, but otherwise
> > if you want some C++ code bu
> On Aug 6, 2014, at 2:10 AM, Marek Polacek wrote:
>
>> On Wed, Aug 06, 2014 at 11:04:14AM +0200, Richard Biener wrote:
>>> On Wed, Aug 6, 2014 at 10:48 AM, Jakub Jelinek wrote:
>>> - libstdc++ ABI changes (it is a significant user visible change,
>>> if you rebuild everything, no extra effor
On Wed, 6 Aug 2014, Jakub Jelinek wrote:
- libstdc++ ABI changes
It seems unlikely to be in the next release, it is too late in the cycle.
Chances to break the ABI don't come often, and rushing one at the end of
stage1 would be wasting a good opportunity.
--
Marc Glisse
On Wed, Aug 06, 2014 at 11:20:01AM +0200, Marc Glisse wrote:
> On Wed, 6 Aug 2014, Jakub Jelinek wrote:
>
> >- libstdc++ ABI changes
>
> It seems unlikely to be in the next release, it is too late in the cycle.
> Chances to break the ABI don't come often, and rushing one at the end of
> stage1 wo
On 6 August 2014 10:06, Jakub Jelinek wrote:
> On Wed, Aug 06, 2014 at 11:04:14AM +0200, Richard Biener wrote:
>> > - libstdc++ ABI changes (it is a significant user visible change,
>> > if you rebuild everything, no extra effort is needed, but otherwise
>> > if you want some C++ code built wit
On Wed, Aug 6, 2014 at 12:08 PM, Jonathan Wakely wrote:
> On 6 August 2014 10:06, Jakub Jelinek wrote:
>> On Wed, Aug 06, 2014 at 11:04:14AM +0200, Richard Biener wrote:
>>> > - libstdc++ ABI changes (it is a significant user visible change,
>>> > if you rebuild everything, no extra effort is ne
On Wed, Aug 6, 2014 at 12:20 PM, Richard Biener
wrote:
> On Wed, Aug 6, 2014 at 12:08 PM, Jonathan Wakely
> wrote:
>> On 6 August 2014 10:06, Jakub Jelinek wrote:
>>> On Wed, Aug 06, 2014 at 11:04:14AM +0200, Richard Biener wrote:
> - libstdc++ ABI changes (it is a significant user visible
On 6 August 2014 11:20, Richard Biener wrote:
> On Wed, Aug 6, 2014 at 12:08 PM, Jonathan Wakely
> wrote:
>> On 6 August 2014 10:06, Jakub Jelinek wrote:
>>> On Wed, Aug 06, 2014 at 11:04:14AM +0200, Richard Biener wrote:
> - libstdc++ ABI changes (it is a significant user visible change,
>>
On Wed, Aug 06, 2014 at 12:20:04PM +0200, Richard Biener wrote:
> >> No, AFAIK it is also -std=c++98. At least my understanding was that
> >> std::list and std::string are going to change ABI (and get new abi_tag)
> >> in all C++ modes. Jonathan/Jason/Paolo, is that right?
> >
> > Correct. We wan
On Wed, Aug 6, 2014 at 12:25 PM, Jonathan Wakely wrote:
> On 6 August 2014 11:20, Richard Biener wrote:
>> On Wed, Aug 6, 2014 at 12:08 PM, Jonathan Wakely
>> wrote:
>>> On 6 August 2014 10:06, Jakub Jelinek wrote:
On Wed, Aug 06, 2014 at 11:04:14AM +0200, Richard Biener wrote:
> > - li
On Wed, 6 Aug 2014, Richard Biener wrote:
It's an ABI change for all modes (but not a SONAME change because the
old and new definitions will both be present in the .so).
Ugh. That's going to be a nightmare to support.
Yes. And IMO a waste of effort compared to a clean .so.7 break, but
well
On Wed, Aug 06, 2014 at 12:31:57PM +0200, Richard Biener wrote:
> Ok, so the problematical case is
>
> struct X { std::string s; };
> void foo (X&);
Yeah.
> then. OTOH I remember that then mangling of X changes as well?
Only if you add abi_tag attribute to X.
I hope the libstdc++ folks will ad
On Wed, Aug 06, 2014 at 12:35:02PM +0200, Marc Glisse wrote:
> >>>It's an ABI change for all modes (but not a SONAME change because the
> >>>old and new definitions will both be present in the .so).
> >>
> >>Ugh. That's going to be a nightmare to support.
>
> Yes. And IMO a waste of effort compar
On Wed, 6 Aug 2014, Jakub Jelinek wrote:
On Wed, Aug 06, 2014 at 12:31:57PM +0200, Richard Biener wrote:
Ok, so the problematical case is
struct X { std::string s; };
void foo (X&);
Yeah.
then. OTOH I remember that then mangling of X changes as well?
Only if you add abi_tag attribute to
On Wed, Aug 6, 2014 at 12:50 PM, Marc Glisse wrote:
> On Wed, 6 Aug 2014, Jakub Jelinek wrote:
>
>> On Wed, Aug 06, 2014 at 12:31:57PM +0200, Richard Biener wrote:
>>>
>>> Ok, so the problematical case is
>>>
>>> struct X { std::string s; };
>>> void foo (X&);
>>
>>
>> Yeah.
>>
>>> then. OTOH I r
On 5 August 2014 19:32, Роман Донченко wrote:
> Hello,
>
> Tags for the following releases are not in the Git mirror repository:
>
> * 3.3
> * 3.3.1
> * 3.3.5
> * 3.3.6
> * 4.7.4
> * 4.8.3
> * 4.9.1
>
> I figure this is the place to report it?
Yes, this is the right place, thanks. The tags in th
On 08/05/2014 10:21 AM, Prathamesh Kulkarni wrote:
Hi,
I have written notes on "GCC re-architecture BOF"
presented at the Cauldron. I would be grateful if you would
review it for me.
Seems to cover the core parts well... all subject to change as we go
tho :-)
initial focus wlll be the ty
On 6 August 2014 11:31, Richard Biener wrote:
> Ok, so the problematical case is
>
> struct X { std::string s; };
> void foo (X&);
Wouldn't it be even more troublesome with an application that dynloads
dsos depending on user input.
The install script might check if the dso with the right soname i
Hi Art,
> I tried the '--without-gnu-ld --with-ld=/usr/ccs/bin/ld' configure options
> and my build failed again as my GNU 'ld' binary was again being found. So
strange: I'd have expected for gcc to honor a full path in --with-ld
(and --with-ls for that matter). But then I never tried this befor
On Wed, Aug 06, 2014 at 12:33:42PM +0100, Joern Rennecke wrote:
> On 6 August 2014 11:31, Richard Biener wrote:
> > Ok, so the problematical case is
> >
> > struct X { std::string s; };
> > void foo (X&);
>
> Wouldn't it be even more troublesome with an application that dynloads
> dsos depending
On Tue, 2014-08-05 at 03:18 +0530, Prathamesh Kulkarni wrote:
> Hi,
>Please find attached my notes on "libgccjit.so - An experimental
> JIT library using GCC as backend". I would be grateful if you would
> review it for me.
Looks good to me
Dave
On Tue, 2014-08-05 at 03:20 +0530, Prathamesh Kulkarni wrote:
> Hi,
> Please find attached my notes on "A proposal on type-safe RTL".
> I would be grateful if you would review it for me.
>
> Thanks,
> Prathamesh
>
> A proposal for type-safe RTL
>
> Author: David Malcolm
>
>RTL is a l
Hi,
These are my notes for "Machine guided energy efficient
compilation" presented at Cauldron.
Machine guided energy efficient compilation.
Author: Jeremy Bennett
MAGEEC (Machine guided energy efficient compilation),
is a plugin for GCC and other compilers, which includes a
machine learn
Hi,
I have written notes for "libabigail - Towards Better ABI
compatibility checking" presented at Cauldron. I would be
grateful if you would review it for me.
libabigail - Towards Better ABI compatibility checking
Author: Dodji Seketeli
libabigail (Library for ABI generic analysis and
in
Hi,
I have written notes for "GNU C library" BOF presented at
Cauldron. I would be grateful if you would review it for me.
GNU C library BOF
Author: Carlos O'Donell
glibc (GNU C library) is available on most GNU systems
with the Linux kernel. It follows all relevant standards including
I
Jakub,
I've looked into how to implement the openacc kernels directive in gcc.
In order to map the loopnests marked by the kernels directive efficiently on
accelerator hardware, we need parallelization and vectorization.
Focussing on paralellization for the moment, a possibility for paralelli
Dear
How are you?
I have a very Lucrative and Life Changing Business Opportuinity for you.
You can also check on my Biography from this link as well (
http://bank.hangseng.com/1/2/about-us/directors-organisation/board-of-directors
).
This is my email:sarah.legg...@gmail.com
I hope to hear fro
I found the root cause.
In function rs6000_preferred_reload_class, it specifically check the
case that reload 0 into a VSX register, then the target reload class
is VSX register. VSX instructions can't load a constant into VSX
registers directly, I guess the author wanted to use a SUB or XOR
instr
Accessing https://gcc.gnu.org/viewvc/gcc/trunk/
Says it is showing 38 files. But in fact, it shows only the first 25. As an
example, libstdc++-v3 is missing.
Same thing happens in other parts of the tree.
I checked the HTML page source, and the files simply aren't there.
David
On Aug 6, 2014, at 2:38 PM, David Gero wrote:
> Accessing https://gcc.gnu.org/viewvc/gcc/trunk/
>
> Says it is showing 38 files. But in fact, it shows only the first 25. As an
> example, libstdc++-v3 is missing.
>
> Same thing happens in other parts of the tree.
>
> I checked the HTML page
Hi,
On 08/06/2014 08:48 PM, paul_kon...@dell.com wrote:
On Aug 6, 2014, at 2:38 PM, David Gero wrote:
Accessing https://gcc.gnu.org/viewvc/gcc/trunk/
Says it is showing 38 files. But in fact, it shows only the first 25. As an
example, libstdc++-v3 is missing.
Same thing happens in other
On Aug 6, 2014, at 2:59 PM, Paolo Carlini wrote:
> Hi,
>
> On 08/06/2014 08:48 PM, paul_kon...@dell.com wrote:
>> On Aug 6, 2014, at 2:38 PM, David Gero wrote:
>>
>>> Accessing https://gcc.gnu.org/viewvc/gcc/trunk/
>>>
>>> Says it is showing 38 files. But in fact, it shows only the first 25
>Hi,
>
>On 08/06/2014 08:48 PM, paul_kon...@dell.com wrote:
>> On Aug 6, 2014, at 2:38 PM, David Gero wrote:
>>
>>> Accessing https://gcc.gnu.org/viewvc/gcc/trunk/
>>>
>>> Says it is showing 38 files. But in fact, it shows only the first 25. As
>>> an example, libstdc++-v3 is missing.
>>>
>>> S
Hi,
On 08/06/2014 09:19 PM, David Gero wrote:
Wow. What an amazingly unintuitive widget. I looked all over the page
for a "Next 25 files" button. A "Go To" button that doesn't talk about
next 25 files meant nothing. ViewVC used to display all the files.
This is a giant leap backward in the Use
On Wed, 2014-08-06 at 21:34 +0200, Paolo Carlini wrote:
> Hi,
>
> On 08/06/2014 09:19 PM, David Gero wrote:
> > Wow. What an amazingly unintuitive widget. I looked all over the page
> > for a "Next 25 files" button. A "Go To" button that doesn't talk about
> > next 25 files meant nothing. ViewVC
On 6 August 2014 20:12, wrote:
> But the preferred answer in my mind is to get rid of this thing and go back
> to displaying the whole page. If you do want to keep the subset thing, at
> least make it NOT the default.
IIRC that causes timeouts when the site is busy, because it has to
fetch a
Snapshot gcc-4.9-20140806 is now available on
ftp://gcc.gnu.org/pub/gcc/snapshots/4.9-20140806/
and on various mirrors, see http://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 4.9 SVN branch
with the following options: svn://gcc.gnu.org/svn/gcc/branches
On Tue, Aug 05, 2014 at 08:18:06PM -0400, Ulrich Drepper wrote:
> On Tue, Aug 5, 2014 at 12:57 AM, Alan Modra wrote:
> > What version linker? In particular, do you have the fix for PR12975?
>
> The Fedora 19 version. I think it hasn't changed since then which
> means it is 2.23.88.0.1-13 (from
On 07/28/2014 17:38, Matthew Fortune wrote:
> I'll switch to replying on PR61538. I had not read all the ticket
> previously and although I may have found a problem it seems it may not
> be the cause of this failure.
>
> The generated code differences after the patches seem significant but
> I may
46 matches
Mail list logo
