Re: GFDL/GPL issues

* Robert Dewar: >> Duplication is how other GNU projects handle this. For instance, many >> Emacs Lisp functions are documented twice: once as a docstring in the >> source code (which is roughly equivalent to the comment-in-spec >> approach), and once in the Elisp reference (which is GFDLed). > >

Re: GFDL/GPL issues

* Robert Dewar: > Does *anyone* print documentation "out as a book", this seems to me > to be a completely obsolete concept. People still buy books which are available freely in electronic form. This means that some printing still goes on. It might also be necessary to consider what it means whe

Re: GFDL/GPL issues

* Robert Dewar: >> People still buy books which are available freely in electronic form. >> This means that some printing still goes on. > > I think there is a difference between a novel you can hold and > read, and computer documentation. My question was not whether > anyone reads books any more,

Re: GFDL/GPL issues

* Robert Dewar: > In the case of interfaces to library routines, what we do > is to have fully commented Ada package specs that act as > both the documentation of the implementation interface and > as the user documentation (for an example, look at g-spipat.ads). > I can't see any value in duplica

Re: GFDL/GPL issues

* Joel Sherrill: >> This approach is far less useful for languages which haven't got >> separate spec files because it encourages programmers of client code >> to look at the implementation, potentially picking up implementation >> details. It encourages the documentation writer to accidentally r

Re: Add uninitialized attribute?

* H. J. Lu: > Sometime I have to do > > int x = 0; > > to silence gcc from uninitialized warnings when I know it is > unnecessary. I guess the official idiom is int x = x; and it is somewhat used in the GNU project although it is not portable.

Re: Add uninitialized attribute?

* Andrew Haley: > On 08/21/2010 10:43 AM, Florian Weimer wrote: >> * H. J. Lu: >> >>> Sometime I have to do >>> >>> int x = 0; >>> >>> to silence gcc from uninitialized warnings when I know it is >>> unnecessary. >> >

Re: get "stack smasshing" for code that uses pointers passed as references.

* Wendell Nichols: > I have some code that passes pointers like: > > int foo( int a,char *& word){ > ... > } > > If that function modifies the actual pointer word (indexes it for > instance) I will get a stack smashing error at runtime. The code runs > perfectly if I set -fno-stack-protector. > >

Re: GNAT building fails on MinGW wiith gcc-4.6.020100904 weekly snapshot

* koala: > When trying to build gnat from this snapshot, i had an issue at line > 280 from gcc/ada/g-socthi-mingw.adb due to: > > g-socthi.adb:280:45 value not in range of type "Interfaces.C.unsigned" > g-socthi.adb:280:45 static expression fails Constraint-check > Is it all an known issue ? > > T

Re: GNAT building fails on MinGW wiith gcc-4.6.020100904 weekly snapshot

* Florian Weimer: > Can you look at the generated s-soscons.ads file? I suspect that the > default > > #ifndef MSG_WAITALL > # define MSG_WAITALL -1 > #endif > CND(MSG_WAITALL, "Wait for full reception") > > kicks in and sets MSG_WAITALL to -1. > >

[Ada] SCIL file generation in the trunk

Is this supposed to work (it seems to me that -gnatC is silently ignored), and is the generated file format documented somewhere?

Re: GCC Bugzilla upgrade to version 3.6.2 ready

* Frédéric Buclin: > If nothing severe is found in the coming days, we will probably upgrade > the production installation later this week. I think Ian will keep you > informed about this. It seems that the new Bugzilla does not set a Message-ID header when sending mail. While this is not a viol

Re: GCC and out-of-range constant array indexes?

* Geert Bosch: > The Ada front end has very extensive warnings. I don't think > they really contribute measurably to performance. > We don't try to construct call graphs to determine > wether the array reference will be executed or not. > If the line appears in your program, it will cause an > err

Re: Discussion about merging Go frontend

* Ian Lance Taylor: > The Go frontend was approved for inclusion with gcc by the steering > committee a while back: http://gcc.gnu.org/ml/gcc/2010-01/msg00500.html . How general is the garbage collector and its support infrastructure in the compiler? AFAICS, it's precise, unlike the Boehm/Dehmer

operator new[] overflow (PR 19351)

Mozilla seems to receive a report of an exploitable operator new[] overflow every couple of months now. Obviously, this is not good. What is necessary so that GCC can fix this code generation issue? I've created a patch, together with a test case, but it has not been approved, nor have I been tol

Re: operator new[] overflow (PR 19351)

* Chris Lattner: > On overflow it just forces the size passed in to operator new to > -1ULL, which throws bad_alloc. This is also what my patch tries to implement.

Re: operator new[] overflow (PR 19351)

* Joe Buck: > It's wasted code if the multiply instruction detects the overflow. > It's true that the cost is small (maybe just one extra instruction > and the same number of tests, maybe one more on architectures where you > have to load a large constant), but it is slightly worse code than what

build_int_cstu does not work as advertised

Trunk has this: | /* Create an INT_CST node with a CST value zero extended. */ | | static inline tree | build_int_cstu (tree type, unsigned HOST_WIDE_INT cst) | { | return double_int_to_tree (type, uhwi_to_double_int (cst)); | } But the comment is misleading because of: | /* Constructs tree

Re: build_int_cstu does not work as advertised

* Richard Guenther: >> If I don't want sign extension, what function should I use instead? >> Should I just call build_int_cst_wide directly? > > You should use a different type, one that is not sign-extended. > Non-canonical constants are not allowed as we share them based on > type and value. I

Re: Dumb idea for accelerating FOSS development

* Ian Lance Taylor: > Bill Cox writes: > >> $ gcc myprog.c -lgit://github/~waywardgeek/sonic=0.1 > > In Go we have a program goinstall which looks at import statements and > pulls in required libraries, where the libraries are named based on > where the sources live. A similar process could

Does TYPE_MAX_VALUE (size_type_node) overflow?

I get strange warnings when I do arithmetic involving TYPE_MAX_VALUE (size_type_node), in particular this code: /* Multiplies MUL1 with MUL2, and adds ADD. Returns (size_t)-1 if the result cannot be be represented as a size_t value. If ADD is null_tree, treat it as a zero constant. */ tre

Re: Does TYPE_MAX_VALUE (size_type_node) overflow?

* Richard Guenther: > On Wed, Jan 19, 2011 at 10:53 PM, Florian Weimer wrote: >> I get strange warnings when I do arithmetic involving TYPE_MAX_VALUE >> (size_type_node), in particular this code: >> >> /* Multiplies MUL1 with MUL2, and adds ADD.  Returns (size_t)-1 i

Re: Does TYPE_MAX_VALUE (size_type_node) overflow?

* Richard Guenther: >> Thanks for the suggestion.  TYPE_MAX_VALUE (sizetype) appears to be >> -1, as the result of this code in stor-layout.c: >> >>  /* sizetype is unsigned but we need to fix TYPE_MAX_VALUE so that it is >>     sign-extended in a way consistent with force_fit_type.  */ >>  max =

Re: operator new[] overflow (PR 19351)

* Gabriel Dos Reis: >>> Still, it's certainly an improvement on the current >>> situation and the cost is negligible compared to the call to the >>> allocator.  Since it's a security issue, some form of the patch should >>> go in. >> >> Well, should I resubmit, with the fix for the problem buildin

Re: GCC 4.1.0 Released

* H. J. Lu: > Here are diffs of SPEC CPU 2K between before and after with gcc 4.1 > using "-O2 -ffast-math" on Nocona: And what about Opterons? IOW, how "generic" is the optimization?

Re: Coverity Open Source Defect Scan of gcc

* Ben Chelf: > Right now, we're guarding access to the actual defects that we > report for a couple of reasons: (1) We think that you, as developers > of gcc, should have the chance to look at the defects we find to patch > them before random other folks get to see what we found and (2) From a >

Re: GCC Compiler Engineer job (I am not a recruiter)

* Mark Mitchell: > 1. What do we do if people do advertise jobs that are not free software > jobs, or not purely free software jobs? How pure is pure? Does "Port > GCC to proprietary OS" count as free or not? And: Does porting GCC to a new processor, to run on a free operating system, without e

Re: SVN: Checksum mismatch problem

* Bruce Korb: > CF: http://gcc.gnu.org/ml/gcc/2005-11/msg00950.html >http://gcc.gnu.org/ml/gcc/2005-11/msg00951.html > > Since Google did not yield an answer, I'm re-asking the question, > though with a slightly different file. Help, please, from anybody > knowing how to work around the issue

Re: optimizing calling conventions for function returns

* Jon Smirl: > Is the callstack branch correctly predicted if the routine being > called is complex? At least the AMD CPUs have implemented a special return stack cache, so the answer is probably "yes". > This does eliminate the test./jmp after every function call. Yes, but the test/jump now ha

Re: Question concerning shared libraries in non-standard locations

* Paul Hilfinger: > 2. Remember to include the appropriate -W,l-R option or whatever in >and every compilation. I don't think it's a good idea to compile in rpaths to non-standard (user-specific) directories by default. This can lead to trapdoor rpaths and generally makes the binaries less p

Re: externs and thread local storage

* Richard Henderson: > You're kidding, right? *All* targets have to generate different > code for thread-local storage. If it didn't, it wouldn't be > thread-local, would it? The local/non-local distinction could be encoded as a flag in the load instruction, set by the linker according to the d

Re: expand_divmod algorithm patented?

* Joern Rennecke: > PJ has posted a news pick on Groklaw about a new patent which, afar as I can > tell, claims the algorithm that Tege has contributed to expmed.c:expand_divmod > in 1994 (r7598) > http://www.freshpatents.com/Method-and-apparatus-for-efficient-software-based-integer-division-dt200

Re: SPEC CPU 2006 and gcc

* Toon Moene: > Well, I'd like to order, but it is unclear from the online > documentation whether I'm eligible for the educational / non-profit > price. > > $ 800 is a bit too much - even for my most prominent hobby. I know someone who has received (or is about to receive) a license he probably

Re: libgfortran.so SONAME and powerpc64le-linux ABI changes

* Andreas Schwab: > On Okt 09 2021, Thomas Koenig via Fortran wrote: > >> There is no choice - we need to make object code compiled by the user >> incompatible between the old and the new format on the systems where >> we make the switch. > > If you link, but not recompile, object files compiled a

Re: [PATCH] x86-64: Optimize memset for zeroing

* H. J. Lu via Libc-alpha: > bzero is an alias of SSE2 memset in glibc. Should we add __memsetzero > like __memcmpeq? It should be almost free in glibc. GCC can use > __memsetzero if it is available. bzero does not have the interface ambiguity that bcmp has. So the only reason for not using

Re: [PATCH] x86-64: Optimize memset for zeroing

* H. J. Lu: > On Fri, Dec 31, 2021 at 12:43 PM Florian Weimer wrote: >> >> * H. J. Lu via Libc-alpha: >> >> > bzero is an alias of SSE2 memset in glibc. Should we add __memsetzero >> > like __memcmpeq? It should be almost free in glibc. GCC can u

Re: [PATCH] x86-64: Optimize memset for zeroing

* Noah Goldstein: >> >> bzero does not have the interface ambiguity that bcmp has. So the >> >> only reason for not using it would be namespace cleanliness. >> > >> > bzero isn't a standard C function and it isn't optimized like memset >> > in glibc. > > It could be an issue if the "optimization"

Re: More C type errors by default for GCC 14

* Joseph Myers: > On Wed, 10 May 2023, Eli Zaretskii via Gcc wrote: > >> That is not the case we are discussing, AFAIU. Or at least no one has >> yet explained why accepting those old K&R programs will adversely >> affect the ability of GCC to compile C2x programs. > > At block scope, > > auto

Re: More C type errors by default for GCC 14

* Florian Weimer: > In summary, all these seems to be good candidates for errors by default: > > * int-conversion as errors (already raised separately > * -Wint-conversion for ?: > * parameter names in non-prototype function declarations > * the union wait function pointer co

Re: More C type errors by default for GCC 14

* Gabriel Ravier: > On 5/12/23 19:52, Florian Weimer wrote: >> * Florian Weimer: >> >>> In summary, all these seems to be good candidates for errors by default: >>> >>> * int-conversion as errors (already raised separately >>> * -Wint-conve

Re: More C type errors by default for GCC 14

* Alexander Monakov: > This is not valid (constraint violation): > > unsigned x; > > int *p = &x; > > In GCC this is diagnosed under -Wpointer-sign: > > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=25892 Thanks for the reference. I filed: -Wpointer-sign must be enabled by default

Re: More C type errors by default for GCC 14

* Joseph Myers: > On Fri, 12 May 2023, Florian Weimer wrote: > >> This sone seems to be a good candidate for additional errors, though: >> >> warned_here = pedwarn >> (loc, warn_return_type >= 0 ? OPT_Wreturn_type : 0, >> "% with no value, i

Re: More C type errors by default for GCC 14

* Jason Merrill: > On Fri, May 12, 2023 at 11:03 AM Florian Weimer wrote: >> >> * Joseph Myers: >> >> > On Wed, 10 May 2023, Eli Zaretskii via Gcc wrote: >> > >> >> That is not the case we are discussing, AFAIU. Or at least no one has >&

Re: More C type errors by default for GCC 14

* Sam James: > Florian Weimer writes: > >> [...] >> In summary, all these seems to be good candidates for errors by default: >> >> * int-conversion as errors (already raised separately >> * -Wint-conversion for ?: >> * parameter names in non-prototype

Re: More C type errors by default for GCC 14

* Sam James: > Florian Weimer writes: > >> * Sam James: >> >>> Florian Weimer writes: >>> >>>> [...] >>>> In summary, all these seems to be good candidates for errors by default: >>>> >>>> * int-conversion

Re: Bad interaction between gcc and glibc's handling of GNU extension [GCC PR 115724]

* Jakub Jelinek: > On Tue, Jul 02, 2024 at 12:54:09PM -0400, David Malcolm via Gcc wrote: >> Back in 2007 glibc gained some logic to implement "error" and >> "error_at_line" by splitting into zero and non-zero cases, with the >> nonzero case calling a "noreturn" function [1]. >> >> This doesn't s

Re: Details for svn test repository

* Daniel Berlin: >> You could be right, but I don't see how. Once you've set the revision >> numbers, can you really go back and insert earlier revision numbers? > Only by dumping and reloading. Yes, but you don't want to do this as soon as revision numbers are used in bug reports, mailing list

Re: Details for svn test repository

* Daniel Berlin: > It's not easier to implement. Trying to translate cvs into changesets > is not easy (though the reverse is), unless you do it the stupid way (IE > not try to discover what is a copy and what isn't). > So matching commit for commit won't give you good history. > Especially on br

Re: LC_COLLATE

* Paolo Bonzini: > and these do not include regex character ranges. LC_COLLATE would only > be used for sorting and for string comparisons. You end up with similar behavior if you read the POSIX spec carefully, IIRC. LC_COLLATE should not affect character ranges.

Re: Slightly OT: We should move #gcc off of FreeNode

* Andrew Haley: > Patrick McFarland writes: > > Today lilo (the FreeNode network owner) has decided to make one step away > in a > > direction opposite of freedom, and banned all Tor users from the FreeNode > > network. > > I can't find a statement from FreeNode. There is one, but it's fair

Re: g++ member function .at() for arrays

there. -- Florian Weimer / Red Hat Product Security Team

Re: setjmp/longjmp: Wrong code generation

this one in a reliable fashion, too. -- Florian Weimer / Red Hat Product Security Team

Re: [GSoC] Does this proposal look good?

On 04/23/2013 07:21 PM, Tim Shen wrote: I've made a proposal under the guide of application. Is it detailed and realistic? Out of curiosity, do you plan to use a Thompson automaton where possible, or just NFAs throughout? -- Florian Weimer / Red Hat Product Security Team

Re: [GSoC] Does this proposal look good?

ssions) often negate the wins from a simplified execution model. -- Florian Weimer / Red Hat Product Security Team

pure/const function attribute and memoization

d our documentation say? -- Florian Weimer / Red Hat Product Security Team

Re: pure/const function attribute and memoization

at defines such annotations as valid? I'll think about it. It's not something I can extemporize, -- Florian Weimer / Red Hat Product Security Team

Re: pure/const function attribute and memoization

should warn about memoization and thread safety issues. Trying to come up with more general semantics for const/pure appears to be difficult to impossible, and as you say, does not match what the compiler does today. -- Florian Weimer / Red Hat Product Security Team

Re: Excessive calls to iterate_phdr during exception handling

r some RCU-like approach. But it seems a faster approach is already available, so this is somewhat besides the point. -- Florian Weimer / Red Hat Product Security Team

Re: Generate abs target assembly code with saturation behavior

th N, the value is reduced modulo 2^N to be within range of the type; no signal is raised." <http://gcc.gnu.org/onlinedocs/gcc/Integers-implementation.html#Integers-implementation> -- Florian Weimer / Red Hat Product Security Team

Re: Strange Fortran/C/Java interaction

he Fortran code, depending on the value of the LC_ALL environment variable. Can you reproduce this with OpenJDK 7? -- Florian Weimer / Red Hat Product Security Team

Re: Strange Fortran/C/Java interaction

On 07/04/2013 01:55 PM, Martin Reinecke wrote: On 07/04/13 13:43, Florian Weimer wrote: On 07/04/2013 11:22 AM, Martin Reinecke wrote: The attached testcase requires gcc and gfortran, as well as a JDK installation. When running "make" with gcc/gfortran 4.7.2 and Oracle JDK 1.7, a s

Re: fatal error: gnu/stubs-32.h: No such file

t development environment. -- Florian Weimer / Red Hat Product Security Team

Re: RFC: Gimple combine/folding interface

On 07/20/2013 02:09 AM, Andrew Pinski wrote: gimple_combine(bool reas) : nonzerobitsf(NULL), valueizerv(NULL), allow_full_reassiocation(reas) {} I think this constructor should be marked "explicit". -- Florian Weimer / Red Hat Product Security Team

Re: fatal error: gnu/stubs-32.h: No such file

at's where the error message comes from. I don't think that's easy to change because of the way dpkg handles file conflicts (even if the files are identical) and how true multi-arch support is implemented in Debian. -- Florian Weimer / Red Hat Product Security Team

Re: [x86-64 psABI] RFC: Extend x86-64 PLT entry to support MPX

instructions. Would it be possible to use a different instruction sequence that stays in the 16 byte limit? Or restrict MPX support to BIND_NOW relocations? -- Florian Weimer / Red Hat Product Security Team

Re: fatal error: gnu/stubs-32.h: No such file

arch support is implemented in Debian. But hold on: if I just wanted to compile C programs I'd use the system's C compiler. Anyone building GCC for themself has a reason for doing so. I suspect a fairly common exercise is to check if the trunk still has the bug you're about to

Re: Intel® Memory Protection Extensions support in the GCC

different pages having memory objects of the same size (which happens with some malloc implementations). -- Florian Weimer / Red Hat Product Security Team

Re: Intel(R) Memory Protection Extensions support in the GCC

a bit of memory overhead, but I guess I'll have to wait and see. -- Florian Weimer / Red Hat Product Security Team

Re: Build problem msg: xgcc: error trying to exec 'cc1': execvp: No such file or directory

to the error message. This is probably a question that is more suitable for the gcc-help mailing list. -- Florian Weimer / Red Hat Product Security Team

Re: ilp32 far pointers

* David McQuillan: > Has there been an implementation or design of a way of representing 64 > bit pointers with ilp32 on a 64 bit system? There's the x32 architecture, but I'm not sure if that's what you want.

Re: Error message source line display

are turned on by default. It's also rather long and as such obscures the main command. As far as I know, there's no way to set these options "by default" for GCC, either via environment variables nor via some configuration file. There is, through the specs file. -- Florian Wei

Re: [RFC] Detect most integer overflows.

e if (a + b < c) { and get an infinite-precision result (GNAT already has a mode for that). But only very low-level code should have to use that, and supporting shifts without memory allocation might be difficult. Aborting on overflow will not help the programmer with writing such ch

Re: [RFC] Detect most integer overflows.

nd it will work there. We defined it to be bit-pattern-preserving as a GCC extension, anyway. -- Florian Weimer / Red Hat Product Security Team

Re: [RFC] Apple Blocks extension

On 11/04/2013 06:10 AM, Ian Lance Taylor wrote: Clang's blocks are more powerful than GCC's nested functions, because blocks may be placed on the heap, and therefore returned from a function. And they don't need code generation at run time. -- Florian Weimer / Red Hat Product Security Team

Report on the bounded pointers work

amount of effort. -- Florian Weimer / Red Hat Product Security Team

Re: Why doesn't gcc 4.6 show line numbers in error messages?

ix()' Why is the location of the error shown relative to .text instead of as a simple line number? Such questions should go to the gcc-help mailing list. This is a linker error message. The linker can only report line numbers in some cases if there is debugging information. -- Floria

Re: Report on the bounded pointers work

ndering if the trade-offs have changed since then, considering that it's again en vogue to bootstrap new architectures. It's difficult to tell without more details about that past effort, though. -- Florian Weimer / Red Hat Product Security Team

[C++] Optimizing dynamic_cast to a final C++ class

t-path for final target classes to the __dynamic_cast implementation? -- Florian Weimer / Red Hat Product Security Team

Re: [RFC] Replace Java with Go in default languages

* Richard Biener: > Oh, can we consider dropping java alltogether please? At least we could remove all those pregenerated files.

Re: [RFC] Replace Java with Go in default languages

* Jeff Law: > At least for Linux systems, the bootstrapping problem is largely a > solved problem by the major vendors. Debian is special because GNAT is typically built from a different GCC release than the rest of the distribution because two Ada transitions in a single release cycle are a bit

Re: memset zero bytes at NULL - isolate-erroneous-paths

* Jonathan Wakely: > On 17 November 2013 18:25, Dominic News wrote: >> In the following code (from xorg-server) >> >> if (a == 0) >> addr = 0; >> (...) >> memset(addr, '\0', a); >> >> the path for a==0 is turned into a trap by -fisolate-erroneous-paths. (Is >> calling memset li

Re: memset zero bytes at NULL - isolate-erroneous-paths

* Jeff Law: >> Is this new in C11? Does it apply to functions such as strnlen as well? > No, it's C99 I think. There was a clarification which came in after > C99 which clarified that even if the length is zero, the pointers must > still be valid. Okay, I found the language in sections 7.1.4 a

Re: OpenACC

* Nathan Sidwell: > Targeting PTX, an ISA for use with a single manufacturer's devices, is > not different from targeting the other single-manufacturer ISAs that > GCC already supports. The GCC licensing exception explicitly permits targeting virtual instruction sets, which (to me at least) stron

Re: break in statement expression in while condition fails to compile

id=44715>. I think it's fine to reject such code. -- Florian Weimer / Red Hat Product Security Team

Re: Draft C bindings for IEEE 754-2008 part 4 now available

, but nobody really seems to know what's in it. (It seems that some operations are allowed to be off by an ulp or more, for instance, which I find rather surprising.) -- Florian Weimer / Red Hat Product Security Team

Re: -Wformat-security warnings generated in gcc build

the arg -> "%s", arg transformation unconditionally in the compiler, rendering -Wformat-security pointless. Which is a bit disappointing. -- Florian Weimer / Red Hat Product Security Team

Re: Is C++11 to be default for GCC 4.9?

objections to changing it to "this warning is enabled by default" or "warning enabled by default"? Or is that too verbose? We should show the flag that enables the warning, so that users can use the -Wno- variant to disable it if they want. Or does "enabled by defau

Re: No TBAA before ptr_derefs_may_alias_p?

ll C++ code and vice versa, so it's difficult to consider each language in isolation. -- Florian Weimer / Red Hat Product Security Team

Re: question regarding new warning

would be fine. -- Florian Weimer / Red Hat Product Security Team

Re: Option -pthread in test suite with cross compilers

. I even think you shouldn't link against the library unless you actually create threads. -- Florian Weimer / Red Hat Product Security Team

Running parts of the testsuite

even though I passed --disable-mudflap to ./configure), and no other tests are attempted. This is on x86_64, Fedora 17. Is there currently a way to run only parts of the test suite? If yes, what's the correct make command line? -- Florian Weimer / Red Hat Product Security Team

Re: Running parts of the testsuite

t clear to me, thanks. After some fiddling, I figured out that make check-g++ RUNTESTFLAGS="dg.exp=vla*.C" did the trick for me (that is, no path in the .exp file and the glob pattern). -- Florian Weimer / Red Hat Product Security Team

Re: Merging gdc (GNU D Compiler) into gcc

* Iain Buclaw: > I've have received news from Walter Bright that the license of the D > frontend has been assigned to the FSF. As the current maintainer of > GDC, I would like to get this moved forward, starting with getting the > ball rolling. What would need to be done? And what are the processe

Re: Please sample libcsdbg

requires piping the addresses through addr2line). -- Florian Weimer / Red Hat Product Security Team

Re: C++ and gather-detailed-mem-stats

first stage compiler.) -- Florian Weimer / Red Hat Product Security Team

Re: internal compiler error using lambda and this

error message you get when you try to compile a program which uses type inference in non-C++11 mode. Trunk and 4.7.1 still crash on this example program. Andreas, would you please file a bug in Bugzilla? -- Florian Weimer / Red Hat Product Security Team

Re: GCC stack backtraces

ly testing the patch, but does it handle inline functions? ("addr2line -i" can print multiple source locations for a single stack frame.) Support for /usr/lib/debug would be desirable, too. -- Florian Weimer / Red Hat Product Security Team

Re: GCC stack backtraces

ld Ada (but I'm not sure if you can get a callback when an unhandled exception is raised *before* the stack is unwound). -- Florian Weimer / Red Hat Product Security Team

Re: Request for comments on language extension: Safe arrays and pointers for C.

changes to integer arithmetic will not buy us much. (Oh, and VLAs will never be first-class types in C++, so I'm not sure if it is a good idea to promote their use.) -- Florian Weimer / Red Hat Product Security Team

Re: C++'ization of cp/parser.c/h, limited C++ parsing support for gengtype, Remove dependency of cp/cp-lang.c on cp/parser.h

ached seems nicer to me. -- Florian Weimer / Red Hat Product Security Team

<    1   2   3   4   5   6   7   8   >