hi all,
can someone please comment on the example enclosed?
regards,
michael
2010022400 - goniometrics.tar.gz
Description: GNU Zip compressed data
On Wed, Feb 24, 2010 at 2:43 AM, wrote:
> hi all,
>
> can someone please comment on the example enclosed?
You can only field initialize fields in that class and not in the base class.
Thanks,
Andrew Pinski
After I'm done with supporting Sun symbol versioning in the currently
versioned GCC runtime libraries, I've started investigating versioning
the remaining unversioned ones.
One of them is libffi.so.4. To start, I've looked at the global symbols
in the library with
$ nm -Pgn libffi.so.4 | awk '$2
After I'm done with supporting Sun symbol versioning in the currently
versioned GCC runtime libraries, I've started investigating versioning
the remaining unversioned ones.
One of them is libobjc.so.4. To start, I've looked at the global symbols
in the library with
$ nm -Pgn libobjc.so.4 | awk '
As the last of the shared GCC runtime libraries, libgnat.so and
libgnarl.so lack symbol versioning support and a defined ABI.
Currently, they use libgnat-4.5.so and libgnarl-4.5.so SONAMEs, what
libtool calls release versioning. If the libgnat/libgnarl ABI is really
that fluent that it changes fro
After the recent flurry of patches to implement Sun symbol versioning
for the GCC runtime libraries
PATCH: Support Sun symbol versioning in libstdc++-v3
http://gcc.gnu.org/ml/gcc-patches/2010-02/msg01001.html
PATCH: Support Sun symbol versioning in libgomp
http://g
> As the last of the shared GCC runtime libraries, libgnat.so and
> libgnarl.so lack symbol versioning support and a defined ABI.
> Currently, they use libgnat-4.5.so and libgnarl-4.5.so SONAMEs, what
> libtool calls release versioning. If the libgnat/libgnarl ABI is really
> that fluent that it c
Rainer Orth writes:
> * Several global variables are obviously implementation details, and
> thus not part of the ABI (e.g. idxsize, narrays, nbuckets, nindices).
They should probably be renamed to be namespace-clean.
Andreas.
--
Andreas Schwab, sch...@redhat.com
GPG Key fingerprint = D4E8
I would like to tweak cpp to dump some usage stats from its symbol
table -- like dumping which #defines were not used at all, etc.
I'm wondering if someone can help me figure out where in the code I
would look to start to do this.
(I know that I'll need to add a command-line argument, and I
Victor Norman writes:
> I would like to tweak cpp to dump some usage stats from its symbol
> table -- like dumping which #defines were not used at all, etc.
>
> I'm wondering if someone can help me figure out where in the code I
> would look to start to do this.
libcpp/identifiers.c
Ian
On 02/18/2010 07:46 PM, Joseph S. Myers wrote:
On Thu, 18 Feb 2010, Jason Merrill wrote:
I periodically get bitten by bug 34115: a compiler configured without
--with-arch on i686-pc-linux-gnu doesn't support atomics. I think we would
only need to bump the default to i486 to get atomic support.
[Apologies for the somewhat-off-topic nature of this post, but I felt
it would still be of interest to others on this thread.]
> "Jon" == Jon Turner writes:
Jon> I was well aware of the overhead that gprof can introduce,
Jon> but did not recognize that this overhead was not being
Jon> count
* Rainer Orth:
> Since I barely know any Ada, or Ada mangling,
Ada subprogram name mangling depends on the order of declarations in
the source file. This order is also somewhat constrained by language
rules. I think this means that defining a stable ABI is rather
difficult.
On Thu, Feb 25, 2010 at 12:00 AM, Jason Merrill wrote:
> On 02/18/2010 07:46 PM, Joseph S. Myers wrote:
>>
>> On Thu, 18 Feb 2010, Jason Merrill wrote:
>>
>>> I periodically get bitten by bug 34115: a compiler configured without
>>> --with-arch on i686-pc-linux-gnu doesn't support atomics. I thin
Hi,
I just wrote a little gcc plugin, which can be used to show GIMPLE cfg
graphically when debug gcc. Currently, it's still a very initial
version. It,
* transfers tree dump into vcg file,
* then invokes vcgview (or aisee etc.) to show the graph.
I would like to improve it to support both tr
> > Since I barely know any Ada, or Ada mangling,
>
> Ada subprogram name mangling depends on the order of declarations in
> the source file. This order is also somewhat constrained by language
> rules. I think this means that defining a stable ABI is rather
> difficult.
Not sure what this part
16 matches
Mail list logo