On 23 June 2016 at 01:10, Soul Studios wrote:
> Hi there-
> quick question,
It would have been better on the libstdc++ mailing list.
> does deque as defined in libstdc++ allocate upon initialisation or upon
> first insertion?
Unfortunately our std::deque allocates some memory in its default
cons
On 06/22/2016 07:17 PM, ayush goel wrote:
>
> Hi, I am working on importing gnulib library inside the gcc tree.
> Should the library be imported in the top level directory along with
> other libraries (like libiberty, libatomic, liboffloadmic etc), or
> should it be imported inside gcc/ like it is
A user filed a bug about a bad location in a warning. It was marked as
an "easyhack" in bugzilla, and I had a go at fixing it.
I though it may be useful for new GCC developers if I document what I
did to fix it.
FWIW, the bug was PR c/71610
i.e. https://gcc.gnu.org/bugzilla/show_bug.cgi?id=716
On 23/06/16 12:18, Pedro Alves wrote:
> gdb doesn't put that gnulib wrapper library at the top level, mainly
> just because of history -- we didn't always have that wrapper
> library -- and the fact that gdb/gdbserver/ itself is not at top
> level either, even though it would be better moved to top
On 06/23/2016 17:04, David Malcolm wrote:
> A user filed a bug about a bad location in a warning. It was marked as
> an "easyhack" in bugzilla, and I had a go at fixing it.
>
> I though it may be useful for new GCC developers if I document what I
> did to fix it.
Shouldn't this also go to the wik
On 06/23/2016 03:54 PM, Szabolcs Nagy wrote:
> if both gcc and binutils used a toplevel gnulib directory
> then shared tree build would have the same problem as
> libiberty has now: gcc and binutils can depend on different
> versions of libiberty and then the build can fail.
> as far as i know the
On Thu, Jun 23, 2016 at 5:04 PM, David Malcolm wrote:
> Step 10: commit to svn
>
> Once the patch is approved, commit it to svn. (FWIW I do all of my
> development work in git; I have an svn checkout that I use purely for
> the final checkin, having smoketested the patch first).
Why not checkin
Snapshot gcc-6-20160623 is now available on
ftp://gcc.gnu.org/pub/gcc/snapshots/6-20160623/
and on various mirrors, see http://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 6 SVN branch
with the following options: svn://gcc.gnu.org/svn/gcc/branches/gcc-6
David Malcolm writes:
> A user filed a bug about a bad location in a warning. It was marked as
> an "easyhack" in bugzilla, and I had a go at fixing it.
>
> I though it may be useful for new GCC developers if I document what I
> did to fix it.
>
> FWIW, the bug was PR c/71610
> i.e. https://gc
