Snapshot gcc-4.6-20121026 is now available on
ftp://gcc.gnu.org/pub/gcc/snapshots/4.6-20121026/
and on various mirrors, see http://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 4.6 SVN branch
with the following options: svn://gcc.gnu.org/svn/gcc/branches
This merge brings the branch up to trun revision 192857.
Tested on x86_64.
Diego.
On Fri, Oct 26, 2012 at 3:25 PM, Caroline Tice wrote:
> Ok, here are the patches for the Makefile.am and Makefile.in files. I
> am also having trouble with the following issue: I need to make sure
> that one of the new libraries is linked in with libstdc++ when
> libstdc++ gets built. I have no
Ok, here are the patches for the Makefile.am and Makefile.in files. I
am also having trouble with the following issue: I need to make sure
that one of the new libraries is linked in with libstdc++ when
libstdc++ gets built. I have not been able to successfully figure out
where exactly is the com
On Fri, Oct 26, 2012 at 10:58 AM, Caroline Tice wrote:
>
> I am working on a patch (which I hope to be able to submit in the next
> few days), and I have run into a snag that I am hoping someone can
> help me with.
>
> As part of this patch, I am trying to build two new *.a (static
> archive) libr
I've merged trunk into the gimplefe branch as of rev 192823.
Tested on x86_64.
Diego.
Hello,
I am working on a patch (which I hope to be able to submit in the next
few days), and I have run into a snag that I am hoping someone can
help me with.
As part of this patch, I am trying to build two new *.a (static
archive) libraries in libstdc++-v3/libsupc++. I have modified
Makefile.am
On Fri, Oct 26, 2012 at 2:16 PM, Christophe Lyon wrote:
> I also use some patches posted by Matthew Gretton-Dann, which are
> still under discussion: I will open a PR, and attach these patches
> too. Is it OK?
Yes, that'd be all that's needed to reproduce the bug.
Ciao!
Steven
On 26 October 2012 00:47, Steven Bosscher wrote:
> On Fri, Oct 26, 2012 at 12:26 AM, Andrew Pinski wrote:
>> The official wording from SPEC is that the sources are under the same
>> license as they are provided to them. It is the data files which are
>> under the SPEC license.
>
> Good. So the on
On Fri, Oct 26, 2012 at 1:49 AM, Konstantin Vladimirov
wrote:
> Hi,
>
> Consider I have pattern like:
>
> (define_insn "big_combined_one"
> [(set (match_operand:SI 0 ...)
> (ior:SI (and:SI (lshiftrt:SI (match_operand:SI 1 ...)
> (match_operand:SI 2 ..
10 matches
Mail list logo