On Mon, Sep 12, 2011 at 15:24, Gerald Pfeifer wrote:
> Should this be added to the GCC 4.7 release notes at
> http://gcc.gnu.org/gcc-4.7/changes.html ? If you need help doing
> so, propose a text and I'll be happy to care of it.
I absolutely need help (just ask Diego)... but not with that... 8-
On Sun, Jun 26, 2011 at 07:28, Joseph S. Myers wrote:
> It seems to me that what's really wanted here is to change the add_sysroot
> flag for the C++ path (all of the C++ paths?), rather than adding special
> code to detect paths starting with the sysroot and reinterpret them.
I considered doing
}'.
No changes in test results. (!! usually there are some, only dates this time!)
Also built my special cross configuration, that worked as expected.
OK for trunk?
chris
---
[gcc/ChangeLog]
2011-06-25 Chris Demetriou
* cppdefault.h (cpp_TARGET_SYSTEM_ROOT): New variable.
o building
a -grtev2- compiler as well.
thanks,
chris
[gcc/ChangeLog.google-integration]
2011-06-16 Chris Demetriou
* config/arm/linux-grtev2.h: New file.
* config/arm/linux-elf.h (GLIBC_DYNAMIC_LINKER): Prefix with
RUNTIME_ROOT_PREFIX.
* con
about.)
thanks,
chris
-
[gcc/ChangeLog.google-4_6]
2011-06-09 Chris Demetriou
Backport from google/main r174890:
2011-06-09 Chris Demetriou
* doc/install.texi (--with-warn-frame-larger-than-extra-text): New.
* configure.ac (--with-warn-frame-larger-than-extra
[resending plain text. Sorry for the noise.]
[sorry, i got stuck doing a bunch of other things.]
On Fri, May 6, 2011 at 10:05, Andrew Pinski wrote:
>
> On Fri, May 6, 2011 at 1:52 AM, Chris Demetriou wrote:
> > In theory, a more general warning-text-addition mechanism could be use
On Thu, May 5, 2011 at 12:19, Andrew Pinski wrote:
> Is there a reason why this cannot be an option that someone passes on
> the command line of GCC instead of a configure option?
I don't think we ever considered that approach.
That's actually a great idea, I think better for our purposes than a
egressions). Manually tested that the resulting warning
looks right, too.
OK for google/main?
chris
---
[gcc/ChangeLog.google-main]
2011-05-05 Chris Demetriou
* doc/install.texi (--with-warn-frame-larger-than-extra-text): New.
* configure.ac (--with-warn-frame-larger-than-extra-
Diego,
Testing w/ ubuntu lucid native bootstrap + check (C/C++), with --with-pic
and numerous other flags, looking good.
OK for google/main (assuming tests succeed)?
chris
--
[libgcc/ChangeLog.google-main]
2011-05-04 Chris Demetriou
Backport from trunk r173391:
2011-05-04
On Wed, May 4, 2011 at 00:52, Chris Demetriou wrote:
> Ian, per your previous comment (which I read as pre-approval for this
> change 8-), I'm planning to commit the attached as soon as it's done
> testing.
>
>
> chris
> -
> [libgcc/Change
On Tue, May 3, 2011 at 16:39, Chris Demetriou wrote:
> > It is also OK if you s/__i686/__x86/ to correspond to your earlier
> > change. Either way is OK.
>
> Well, that change is not in trunk.
> Should that change move to trunk, yes, it's appropriate to change this
>
On Tue, May 3, 2011 at 15:05, Ian Lance Taylor wrote:
>
> > 2011-05-03 Chris Demetriou
> >
> > * libgcc/config/i386/morestack.S (__i686.get_pc_thunk.bx): New.
>
> No "libgcc" in libgcc/ChangeLog.
Fixed, sorry. (That's what I get for pasting
figured as normal, and also --with-pic.
No regressions before/after.
Ian, OK for trunk?
chris
[libgcc/ChangeLog]
2011-05-03 Chris Demetriou
* libgcc/config/i386/morestack.S (__i686.get_pc_thunk.bx): New.
[libgcc/ChangeLog]
2011-05-03 Chris Demetriou
* libgcc/config/i386/m
On Mon, May 2, 2011 at 11:49, Andrew Pinski wrote:
> On Sat, Apr 30, 2011 at 2:14 PM, Chris Demetriou wrote:
>> Makes -S output more easily preprocessable -- otherwise, the __i686 in
>> __i686.get_pc_think.reg chokes things.
>
> IIRC the reason why it uses __i686 is becaus
trunk, but if
somebody wants it... great! 8-)
chris
---
[gcc/ChangeLog.google-main]
2011-04-30 Chris Demetriou
* config/i386/i386.c (get_pc_thunk_name): Make 32-bit
thunk prefix be __x86.get_pc_thunk.
[gcc/ChangeLog.google-main]
2011-04-30 Chris Demetriou
* config/i386/i386.c
about not attempting to address the issues
raised in PRs 40989 and 48088 where -Werror= and -Wno-error= don't
work as expected... but I'm at a loss for a concise set of words to
describe the problems and it's late. 8-S)
chris
---
2011-03-12 Chris Demetriou
*
16 matches
Mail list logo
