On Wed, Mar 27, 2013 at 2:04 PM, Nenad Vukicevic wrote:
> The latest Fedora Core 18 comes with automake 1.12.1 and perl 5.16.2. I
> installed and tried to use automake 1.11.1 for one of the GCC libraries, but
> got a warning from aclocal:
>
> main::scan_file() called too early to check prototype a
This page: http://gcc.gnu.org/gcc-4.8/
under "release history" says GCC 4.8 was released on March 22, 2012.
This should be 2013, not 2012.
The latest Fedora Core 18 comes with automake 1.12.1 and perl 5.16.2. I
installed and tried to use automake 1.11.1 for one of the GCC libraries,
but got a warning from aclocal:
main::scan_file() called too early to check prototype at
/usr/local/bin/aclocal line 617.
The latest 1.11.6 has the
> "Lawrence" == Lawrence Crowl writes:
Lawrence> Are the symbol searches specific to the scope context, or does it
Lawrence> search all globally defined symbols?
I am not totally certain in this case, but in gdb many searches are
global, so that "print something" works even if "something" is
On Mar 27, 2013, at 1:02 AM, Senthil Kumar Selvaraj
wrote:
> global-used-types.c in gcc/testsuite/gcc.dg/debug/dwarf2 only specifies
> -g in dg-options. For a target that is not configured to generate
> dwarf-2 by default, the test fails looking for specific DWARF strings in
> the generated assem
On Wed, 27 Mar 2013, Senthil Kumar Selvaraj wrote:
> Hi,
>
> I was looking at why gcc.dg/c1x-align-3.c (test for errors, line 15) is
> failing for the AVR target, and I found that the test expects _Alignas
> with -__INT_MAX__ - 1 to fail with a "too large" error.
It expects either an error eithe
Hi,
I posted a while ago about a project between Embecosm and the University of
Bristol. In this project we explored the effect that a wide range of
optimisations had on the execution time and energy consumption of a variety of
benchmarks. The project has been written up, and results and conclu
Hi,
I was looking at why gcc.dg/c1x-align-3.c (test for errors, line 15) is
failing for the AVR target, and I found that the test expects _Alignas
with -__INT_MAX__ - 1 to fail with a "too large" error.
I looked at the code responsible for generating the error (c-common.c,
check_user_alignment) a
> While working with some splitters I noticed that the RTL optimisation
> passes do not optimise away a no-op wrapped in a cond_exec.
>
> So for example, if my splitter generates something like:
> (cond_exec (lt:SI (reg:CC CC_REGNUM) (const_int 0))
>(set (match_dup 1)
>
On 27 March 2013 10:05, Richard Biener wrote:
> On Tue, Mar 26, 2013 at 6:30 PM, Frederic Riss
> wrote:
>> Here, the code trying to expand a signed by unsigned widening multiply
>> explicitly checks that the operand isn't a constant. Why is that? I
>> removed that condition to try to find the fa
On 27 March 2013 10:10, Richard Biener wrote:
> On Tue, Mar 26, 2013 at 6:55 PM, Frederic Riss
> wrote:
>> The cost arrays are filled up to
>> MAX_BITS_PER_WORD, thus as a temporary workaround I have defined
>> MAX_BITS_PER_WORD to 64, and I have softened the checks to fail only
>> above MAX_BIT
On Wed, Mar 27, 2013 at 3:13 AM, Nikhil Patil wrote:
> Hello everyone,
>
> I am trying to understand the points-to analysis ("pta") ipa pass, but
> I am not able to match the information generated by the pass and that
> in structure "SSA_NAME_PTR_INFO".
>
> For the code segment,
>
> --
On Tue, Mar 26, 2013 at 6:55 PM, Frederic Riss wrote:
> While working on having the divisions by constants optimized by my GCC
> targeting, I realized that whatever *muldi3_highpart my backend
> provides, it would never be used because of the bounds checks that
> expmed.c does on the cost arrays.
On Tue, Mar 26, 2013 at 6:30 PM, Frederic Riss wrote:
> I was playing with adding support of the various modes of widening
> multiplies on my backend, and hit some restrictions in the expansion
> code that I couldn't explain to myself. These restrictions only impact
> the signed by unsigned versio
Hi,
global-used-types.c in gcc/testsuite/gcc.dg/debug/dwarf2 only specifies
-g in dg-options. For a target that is not configured to generate
dwarf-2 by default, the test fails looking for specific DWARF strings in
the generated assembly.
The patch below changes dg-options to -gdwarf-2. Can someo
15 matches
Mail list logo