I found my problem - I had forgotten about the cloned and generated
constructors.
For this case, there were 9 constructors generated - 3 sets of three with names
of 'CTestClass', '__base_ctor' and '__comp_ctor'. The first two sets of
constructors took references as arguments, I'm assuming copy
> -Original Message-
> From: gcc-ow...@gcc.gnu.org [mailto:gcc-ow...@gcc.gnu.org] On Behalf Of
> Umesh Kalappa
> Sent: Wednesday, January 29, 2014 4:36 AM
> To: gcc@gcc.gnu.org
> Subject: Enable debug info
>
> Dear All,
>
> We need to support the debug info emit for our private port on
Hi Gerald,
Thank you for fixing this. I'm glad to hear that a permanent
workaround will be there in 4.8.3.
Cheers,
Gleb
On Mon, Jan 27, 2014 at 4:27 AM, Gerald Pfeifer wrote:
> Hi Gleb,
>
> On Sun, 26 Jan 2014, Gleb Smirnov wrote:
>> I have been browsing the online docs here:
>> http://gcc.gnu.
Hi All,
Was porting gcc 4.8.1 to the private target which has 8 bit regs and
can be used as pair for 16bit like AB ,CD but not BC or AD.
I was stuck in the type promotion like
int i;
unsigned char c;
int test ()
{
i =c;
}
defined the zero_extendqihi2 pattern for the above c construct lik
On 01/29/2014 09:36 AM, Umesh Kalappa wrote:
> I was in impression using option -g in the commandline by defualt
> ,will emit the dwarf debugging symbols and the info ,But i was wrong
> here.
It usually does.
Andrew.
Dear All,
We need to support the debug info emit for our private port on gcc 4.8.1.
I was in impression using option -g in the commandline by defualt
,will emit the dwarf debugging symbols and the info ,But i was wrong
here.
Anyone in the group point me some references or through some lights o
On Tue, Jan 28, 2014 at 4:17 PM, Bingfeng Mei wrote:
> I checked vectorization code, it seems that only relevant place
> vec_widen_mult_even/odd & vec_widen_mult_lo/hi are generated is in
> supportable_widening_operation. One of these pairs is selected, with priority
> given to vec_widen_mult_e
