On Thu, 2016-02-18 at 00:21 +0100, Stefan Sobernig wrote:
> Am I supposed to file this as a bug report then, for the records? Or
> will it be taken care of ...
Jakub already did all the work. Bug filed, patch written, reviewed and
committed. Plus followup fixup. He is amazing:
https://gcc.gnu.org/
makes sure we only document
abi that is actually supportable.
Thanks,
Mark
between our
projects, please join us or propose a talk. See the attached Call for
Participation for the details.
Thanks,
Mark
--- Begin Message ---
Valgrind developer room at FOSDEM 2017 (Brussels, Belgium, February 4th).
FOSDEM is a free software event that offers open source communities a
place to
Hi GNU Toolchain Hackers,
On Mon, 2016-10-24 at 17:09 +0200, Mark Wielaard wrote:
> Valgrind will have a developer room at Fosdem on Saturday 4 February
> 2017 in Brussels, Belgium. We are always very interested in ideas on how
> to better integrate with the gcc, glibc, gdb core
:
https://pbs.twimg.com/media/Bp1zl2qCEAAfNPY.jpg:large
Do all GCC contributors get to share all that whisky? :)
Cheers,
Mark
On Mon, Jun 16, 2014 at 12:52:10PM +0200, Andreas Schwab wrote:
> Dan Carpenter writes:
> > Adding "--param allow-store-data-races=0" to the GCC options for the
> > kernel breaks C=1 because Sparse isn't expecting a GCC option with that
> > format.
> Please try --param=allow-store-data-races=0 i
nvidia GPU and/or Intel Xeon Phi?
Thanks!
Mark
usion supported? If so, are they already
supported in the trunk, or only specific branch?
Finally, when will support of Knights Corner (knc) be added to the
trunk and/or one of the branches?
Thanks!
Mark
On Tue, Dec 16, 2014 at 9:22 PM, Tobias Burnus
wrote:
> Mark Farnell wrote:
>> H
the nvptx-tools project mentioned in Tobia's page aiming
at replacing the CUDA toolchain?
Thanks!
Mark
On Wed, Dec 17, 2014 at 9:05 AM, Jakub Jelinek wrote:
> On Wed, Dec 17, 2014 at 08:54:06AM +1300, Mark Farnell wrote:
>> That's good news. Does it mean that if I want
obias Burnus
wrote:
> Mark Farnell wrote:
>> So what parameters will I need to pass to ./configure if I want to
>> support PTX offloading?
>
> Pre-remark: I think that the https://gcc.gnu.org/wiki/Offloading page will be
> updated, once the support has been merged to the
As in the offloading documentation at gcc.gnu.org, currently one must
run ./configure and make for each accelerator and the host itself.
This is very inconvenient and prone to error.
Would it be possible to change the configure script so that all the
user needs to do is to:
* specify the target ho
>From the svn log, I saw tschwinge did a lot of bug fixing on the
gomp-4_0-branch, and recently merged trunk to gomp-4_0-branch without
mention of any outstanding conflicts. Does this signify an imminent
merge of the gomp-4_0-branch to the trunk?
If so, I am really excited to try out openacc
Als
Currently, OpenACC 2.0 is in gomp-4_0-branch, but this email:
https://gcc.gnu.org/ml/gcc/2015-01/msg00032.html
says that gcc 5.0 will enter stage 4 on Friday 16th January, and from
that point onward, only bug fixing patches will be accepted.
So will gomp-4_0-branch be able to be merged into the
p-4.0_branch need to
approach the gcc release team *immediately* and explain why openacc is
essential for gcc 5, and why openacc is ready to merge into the trunk.
We need timely intervention from the gcc release team to ensure
openacc makes it to gcc 5
On Fri, Jan 9, 2015 at 10:09 PM, Tobias Burnus
wrote:
OpenACC 2.0 from reaching the
trunk? And does the GCC core team intend to include OpenACC 2.0 as a
feature of GCC 5.0?
On Fri, Jan 9, 2015 at 9:04 AM, Mark Farnell wrote:
> Currently, OpenACC 2.0 is in gomp-4_0-branch, but this email:
>
> https://gcc.gnu.org/ml/gcc/2015-01/msg00032.html
I know that we are already in stage 4, but features such as OpenACC
2.0, nvptx and KNL (xeon phi) offloading support are so important
for GCC, and if they have to be deferred to GCC 6.0, then it would be
a great loss to GCC, as OpenACC 2.0 makes heterogeneous manycore
programming so much easie
Oh sorry. I just checked out the svn again, and see it already
merged. Well done!
On Tue, Jan 20, 2015 at 11:59 PM, Mark Farnell wrote:
> I know that we are already in stage 4, but features such as OpenACC
> 2.0, nvptx and KNL (xeon phi) offloading support are so important
>
it by
default support offloading to ANY architectures?
Thanks!
Mark
is volatile or when a lower -O level
is used.
dgHandle_t is a uint16_t (unsigned short int) and BS_CFG_DRIVE_GROUPS is
the value 480.
thanks again.
Mark
On 5/18/2015 7:05 PM, Martin Sebor wrote:
On 05/18/2015 02:01 PM, mark maule wrote:
I have a loop which hangs when compiled with -O2, but
On 5/19/2015 10:09 AM, Martin Sebor wrote:
I'm not very familiar with the optimizations that are done in O2 vs O1,
or even what happens in these optimizations.
So, I'm wondering if this is a bug, or a subtle valid optimization that
I don't understand. Any help would be appreciated.
Another
On 5/19/2015 10:28 AM, Andrew Haley wrote:
On 05/19/2015 04:14 PM, mark maule wrote:
Thanks again Martin. I started going down that road yesterday, and got
lost in the forest of options. What I was looking for was some option
that would tell me what was being done with dgHandle
On 5/20/2015 3:27 AM, Richard Biener wrote:
On Mon, May 18, 2015 at 10:01 PM, mark maule wrote:
I have a loop which hangs when compiled with -O2, but runs fine when
compiled with -O1. Not sure what information is required to get an answer,
so starting with the full src code. I have not
On 5/20/2015 2:13 PM, Martin Uecker wrote:
mark maule :
On 5/20/2015 3:27 AM, Richard Biener wrote:
On Mon, May 18, 2015 at 10:01 PM, mark maule wrote:
The usual issue with this kind of behavior is out-of-bound accesses of
arrays in a loop
or invoking undefined behavior when signed
Since the introduction of GNU Property notes this is (sadly) no longer
the correct way to iterate through ELF notes. The padding of names and
desc might now depend on the alignment of the PT_NOTE segment.
https://sourceware.org/ml/binutils/2018-09/msg00359.html
Cheers,
Mark
On Tue, 2019-02-26 at 09:33 +0100, Richard Biener wrote:
> On Mon, 25 Feb 2019, Mark Wielaard wrote:
> > Since the introduction of GNU Property notes this is (sadly) no
> > longer
> > the correct way to iterate through ELF notes. The padding of names
> > and
> &
On Tue, 2019-02-26 at 15:36 +0100, Richard Biener wrote:
> On Tue, 26 Feb 2019, Mark Wielaard wrote:
>
> > On Tue, 2019-02-26 at 09:33 +0100, Richard Biener wrote:
> > > On Mon, 25 Feb 2019, Mark Wielaard wrote:
> > > > Since the introduction of GNU
t has an alignment of 8 then it is a GNU Properties note with the
new layout (at least on GNU systems). Cary did propose some additional
constraints which might be helpful:
https://sourceware.org/ml/binutils/2018-09/msg00359.html
> So - how do I identify a GNU Property note vs. a traditional
> note vs. a gabi one?
>
> Why was the third one added?! (I guess I asked that already...)
Yeah... See above.
Cheers,
Mark
On Tue, Mar 05, 2019 at 02:17:51PM -0700, Martin Sebor wrote:
> The SECURE project adds the function attribute stack_erase that
> serves the purpose described above. It works on stack frames by
> design rather than applying to individual stack objects.
> The presentation they delivered at Cauldron
I got an error message during the push:
>
> remote: hooks/post-receive: line 14: /www/gcc/updatelog: Permission
> denied
> remote: Updating /www/gcc/htdocs/gcc-10/changes.html
/www/gcc/updatelog is where the logs of the post-receive are written.
It was only readable by the gcc group, I did a chmod g+w.
Now things should work without warning.
Cheers,
Mark
Debugging Tools developer room at FOSDEM 2020
(Brussels, Belgium, February 2).
Talk/Discussion Submission deadline: Sunday1 Dec 2019
Devroom Schedule announcement: Sunday 15 Dec 2019
Devroom day: Sunday3 Feb 2020
FOSDEM is a free software
Debugging Tools developer room at FOSDEM 2020
(Brussels, Belgium, February 2).
Talk/Discussion Submission deadline: Sunday1 Dec 2019
Devroom Schedule announcement: Sunday 15 Dec 2019
Devroom day: Sunday2 Feb 2020
FOSDEM is a free software
* Last Reminder! Talk proposal deadline is this weekend! *
Debugging Tools developer room at FOSDEM 2020
(Brussels, Belgium, February 2).
Talk/Discussion Submission deadline: Sunday1 Dec 2019
Devroom Schedule announcement: Sunday 15 Dec 2019
Devroom day:
should be live by Monday.
Should we go with the gcc-reparent.git repo now?
Where exactly should it be installed under https://gcc.gnu.org/git/
Replacing the existing gcc.git will be confusing, but then how would we
name the repo that will become the main git gcc repo in 2 weeks?
Where are the tools/scripts that should be installed on gcc.gnu.org to
keep it up to date during the next 2 week transition period?
Thanks,
Mark
On Mon, 2019-12-16 at 11:29 +, Joseph Myers wrote:
> On Mon, 16 Dec 2019, Mark Wielaard wrote:
>
> > Should we go with the gcc-reparent.git repo now?
>
> I think we should go with the reposurgeon conversion, with all Richard's
> improvements to commit messages. g
e from the actual gcc code tree.
Cheers,
Mark
ly it is still useful.
I will likely delete these again after we have picked a conversion we
actually want to use.
Do we already have a new date for when we are making that decision?
Thanks,
Mark
parate distributions from the C
> compiler & code generator, similarly for the old g77 compiler, gnat,
> etc.
>
> You may find other nuggets in there.
Apparently less complete, but there is also
https://ftp.gnu.org/old-gnu/gcc/
Which does have some old diff files to reconstruct some missing versions.
Cheers,
Mark
o which contains
everything that we were able to salvage and that people could git
remote add if they are really, really interested.
Cheers,
Mark
stable
small/fast builder that reliably warns committers that their commit
broke something extend it to new targets/setups/tests as long as you
can keep the false warnings as close to zero as possible.
Cheers,
Mark
;
> Looks like it should be using /bin/bash not /bin/sh.
>
> --
> Joseph S. Myers
> jos...@codesourcery.com
>
--
Mark Atwood
http://about.me/markatwood
+1-206-604-2198 Mobile & Signal
Ok, thanks. I just get nervous about work thats not backed up.
On Mon, Dec 18, 2017, 4:47 PM Eric S. Raymond wrote:
> Mark Atwood :
> > Where is this work keeping it's working archive? On gitlab?
>
> The master is on grelber in my basement. Copies are synced by Joseph,
>
t be eye-wateringly expensive. Thanks, but I'm not
> > >> going to yell for that help
> > >
> > > I for one would certainly be happy to donate some spare bucks towards
> > > beastie RAM if it helps to get the GCC repo converted to git in a
> > > timely manner, and I'm sure there are other GCC
> > > developers/users/sympathizers who'd be willing to join in. So, where
> > > do we throw those bucks?
> > I'd be willing to throw some $$$ at this as well.
> > Jeff
> >
>
--
Mark Atwood
http://about.me/markatwood
+1-206-604-2198
Jakub, Tobias --
The GCC SC has appointed you as maintainers of libquadmath within GCC.
Please update the MAINTAINERS file to reflect your new positions.
Congratulations!
--
Mark Mitchell
CodeSourcery
m...@codesourcery.com
(650) 331-3385 x713
ntain the port
from this point forward.
Please remember to update the MAINTAINERS file.
Thank you,
--
Mark Mitchell
CodeSourcery
m...@codesourcery.com
(650) 331-3385 x713
be one of the functions that handle the conversion of the
generic tree to the gimple tree.
Again any feedback that would help point me in the right direction would
be appreciated.
Thanks,
=mark
- --
Mark Eklund
Software Engineer
Product Development
mekl...@cisco.com
Cisco Systems, Inc.
170 West
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 3/28/11 10:37 AM, Richard Guenther wrote:
>> On Mon, Mar 28, 2011 at 3:54 PM, Mark Eklund wrote:
>>
>> Again any feedback that would help point me in the right direction would
>> be appreciated.
>>
>
is stored in the type unit DIE
for link-time ODR (one-definition rule) checking. */
I couldn't find where in the toolchain this link-time checking is done.
Does anybody have any pointers?
Thanks,
Mark
teful for all of that and, more generally, for having had the
opportunity to be involved in such an important open-source project.
Thank you,
--
Mark Mitchell
CodeSourcery / Mentor Graphics
m...@codesourcery.com
(650) 331-3385 x713
Uros Bizjak gmail.com> writes:
> For some reason bootstrap on Fedora 16 fails when compiling 32bit
> libjava with undefined reference to `__cxa_call_unexpected':
> [...]
> Googling a bit around the net, it looks that this file is wrongly
> compiled to use C++ exception code, not java exception cod
may never happen on some
platforms (Linux?) since many malloc() implementations will use the
start of a page for their own bookkeeping.
I don't really understand what the testcase is testing. Richard, can
you perhaps shed some light on this?
Thanks,
Mark
---
extern void abort(void);
0
Is there a way to detect that basic blocks have the same range even
though they have different block numbers? Or am I not looking/thinking
about this issue correctly?
Thanks,
Mark
diff --git a/gcc/dwarf2out.c b/gcc/dwarf2out.c
index f9f4295..53776f7 100644
--- a/gcc/dwarf2out.c
+++ b/gcc/dwarf2
On Sun, 2012-01-15 at 19:42 +0100, Mark Wielaard wrote:
> I noticed that when you generate dwarf for an inlined function it often
> comes with duplicate range lists for both the DW_TAG_inlined_subroutine
> and the child DW_TAG_lexical_block DIE.
I filed a bug report for it with some a
go for
exact overlap as a first step). I added a quick and dirty debug_info
scanner that shows equal and (fully) shared ranges to the bug report to
see how much duplication/sharing is going on.
Cheers,
Mark
their
> ports as well.
Great!
> What's the next step?
At the risk of being naive: implement it. I'm not quite sure what
you're looking for here?
I'd assume that we should try to do some of this at the tree->rtl
conversion point, in a platform-independent manner, but I
quot; The GPL is evil and deserves to be struck
down.
Oops - I think this will get me kicked out of the gcc@gcc.gnu.org list. :-)
Cheers,
mark
--
Mark Mielke
ovide tools to introduce or remove prototypes; it's
useful for people who still have (even partially) K&R codebases. And
there are plenty of such people.
--
Mark Mitchell
CodeSourcery
m...@codesourcery.com
(650) 331-3385 x713
7
P30 - 4
--- ---
Total 120 + 3
Previous Report
===
http://gcc.gnu.org/ml/gcc/2009-07/msg00607.html
The next report for 4.5.0 will be sent by Richard.
--
Mark Mitchell
CodeSourcery
m...@codesourcery.com
(650) 331-3385 x713
ird major feature, if we can reach consensus
that it's a good solution to the problem it's set out to solve.
Thanks,
--
Mark Mitchell
CodeSourcery
m...@codesourcery.com
(650) 331-3385 x713
Status
==
The 4.4 branch is open for commits under the usual release branch
rules.
The timing of the 4.4.2 release (at least two months after the 4.4.1
release, so no sooner than September 22) at a point when there are no
P1 regressions open for the branch) has yet to be determined.
Quality
On Tue, Sep 15, 2009 at 8:17 PM, Mark Zweers wrote:
>
> Hello,
>
> While experimenting with "Defaulted and deleting functions" on my brand-newly
> downloaded gcc-4.5 compiler, I've noticed the following: the order of
> '=default' and '
;contribution" step; simple publication may
not be sufficient.
--
Mark Mitchell
CodeSourcery
m...@codesourcery.com
(650) 331-3385 x713
Richard Guenther wrote:
> 2009-09-20 Richard Guenther
>
> * develop.html: Adjust to reflect recent practice.
OK.
--
Mark Mitchell
CodeSourcery
m...@codesourcery.com
(650) 331-3385 x713
ck of active maintenance of GCC, by Apple or otherwise, for
x86 OS X).
Applied.
--
Mark Mitchell
CodeSourcery
m...@codesourcery.com
(650) 331-3385 x713
Index: gcc-4.5/criteria.html
===
RCS file: /cvs/gcc/wwwdocs/htdocs/gcc-4.5/criteria.h
Joern Rennecke wrote:
> But at any rate, the subject does not agree with
> the content of the original post. When we talk
> about a 'regression' in a particular gcc version,
> we generally mean that this version is in some
> way worse than a previous version of gcc.
Didn't the original poster ind
make sense to
me.
--
Mark Mitchell
CodeSourcery
m...@codesourcery.com
(650) 331-3385 x713
or less different about this change then other
mangling changes, as far as I can tell. It's another case where we've
discovered an inability to implement the full language with the current
scheme, and have therefore been forced to make a change.
--
Mark Mitchell
CodeSourcery
m...@codesourcery.com
(650) 331-3385 x713
ather than just a numerical
version. That sounds theoretically right to me, but awfully complicated
in practice.
Do we have another libstdc++ ABI change coming? I'd suggest doing this
as -fabi-version=4, and making that the default at that point.
--
Mark Mitchell
CodeSourcery
m...@codesourcery.com
(650) 331-3385 x713
long as they aren't actually trying
> to share affected data structures.
So, do you consider ABIv3 there only as a theoretical conformance
option? In other words, not something we're going to make the default
in any forseeable future? (Those aren't meant to be rheto
t;. That would be your version 2.1, but arguably more logically
coherent in that it would be expected to move in the future if/when we
find another feature we can't implement due to current mangling issues.
--
Mark Mitchell
CodeSourcery
m...@codesourcery.com
(650) 331-3385 x713
sion.
This still seems a lot of complexity to me, and I still think inserting
a new version between 2 and 3 is odd. If we need the complexity, I
think we have to introduce a new orthogonal option for vector mangling,
independent of the ABI version, but implied by ABI version > 4.
--
Mark Mit
version, but implied by ABI version > 4.
>
> How is mangling orthogonal to the ABI?
It's certainly possible to have ABIv2-with-vector-change and
ABIv2-without. I never claimed that they were the same ABI.
--
Mark Mitchell
CodeSourcery
m...@codesourcery.com
(650) 331-3385 x713
lways pass
-Wno-missing-braces. But, that's not a position I'd argue for strongly.
Whatever we do, I think the C and C++ front-ends should have the same
behavior.
--
Mark Mitchell
CodeSourcery
m...@codesourcery.com
(650) 331-3385 x713
is now:
struct B { struct A a; int j; };
and I write:
struct C c = { 1, 2 };
?
--
Mark Mitchell
CodeSourcery
m...@codesourcery.com
(650) 331-3385 x713
rs, not
-Wmissing-braces. -Wmissing-braces is explicitly about not having all
the brace groups fully specified.
--
Mark Mitchell
CodeSourcery
m...@codesourcery.com
(650) 331-3385 x713
On Wed, 2009-11-18 at 18:19 +0530, M. Mohan Kumar wrote:
> Are VTA patches part of mainline gcc now? If not, where could we get the
> VTA patches?
The VTA implementation is in mainline gcc now. There are also some
backports to gcc 4.4, like the gcc that Fedora 12 ships with.
Cheers,
Mark
On Thu, 2009-11-19 at 19:15 +0530, M. Mohan Kumar wrote:
> On 11/19/2009 04:30 PM, Mark Wielaard wrote:
> > On Wed, 2009-11-18 at 18:19 +0530, M. Mohan Kumar wrote:
> >> Are VTA patches part of mainline gcc now? If not, where could we get the
> >> VTA patches?
> >
f(temp)
before you put in your asm, and if you're in C++ land, you're now
doomed, since creating named temporaries can change the semantics of
programs.
--
Mark Mitchell
CodeSourcery
m...@codesourcery.com
(650) 331-3385 x713
and accepted.
Everybody would have been ready for it, and nobody would be upset. Oh well.
It's been entertaining. gcc@gcc.gnu.org is normally pretty dull to
read... :-)
Cheers,
mark
--
Mark Mielke
if you can
shed any light on this.
Mark
*
This email has been checked by the altohiway Mailcontroller Service
*
> >> Is there any way to improve this behaviour? I have been using 2.9.5
> very
> >> successfully for years and am now looking at 4.4.2, but have many
> such
> >> examples in my code (for clarity of commenting and maintainability).
> >
> > This is very strange. On x86_64, gcc 4.4.1 generates
> >
>
> On Mon, Jan 04, 2010 at 12:18:50PM +0100, Steven Bosscher wrote:
> > > This optimization is done by the first RTL cse pass. I can't
> understand
> > > why it's not being done for your target. I guess this will need a
> > > powerpc expert.
> >
> > Known bug, see http://gcc.gnu.org/PR22141
>
> T
y to fix cse to
> recognize those too.
>
> Andrew
I'm not familiar with the gcc source yet, but just in case I get the time to
look at this, could anyone give me a file/line ref to dive into and examine?
Thanks for your attention on this.
Mark
**
>>> Aha! Yes, that'll probably be it. It should be easy to fix cse to
>>> recognize those too.
>> I'm not familiar with the gcc source yet, but just in case I get the
>> time to look at this, could anyone give me a file/line ref to dive
>> into and examine?
> Would you believe cse.c? :-)
Ha!
compiler/vm implementations easier, not because
of avoiding copyright assignment.
Cheers,
Mark
Steven Bosscher wrote:
> Mark just made an ICE in the compiler with non-default options a P1
> bug for GCC 4.5 (xf.
> http://gcc.gnu.org/ml/gcc-bugs/2010-02/msg01695.html).
>
> Can someone please explain why this kind of bug should be of
> release-blocking priority?
As I wrote
is not marked as P1 regression make sure to mark it as regression
with P3 and CC one of the release managers. Likewise if you think a
bug should not be P1.
In general all regressions toward GCC 4.4 in release critical parts of
the compiler should be P1 at this point if they are build issues, ICEs
this release.
GCC 4.5.1, with corrections for any critical defects reported in GCC
4.5.0, is expected in July, 2010.
As always, a vast number of people contributed to this GCC release --
far too many to thank individually!
--
Mark Mitchell
CodeSourcery
m...@codesourcery.com
(650) 331-3385 x713
t improvements since GCC
4.4.x; they don't all fit in an announcement. Of course, you're
entirely free to publicize plug-ins as you like in any forum you find
appropriate.
--
Mark Mitchell
CodeSourcery
m...@codesourcery.com
(650) 331-3385 x713
Joe Buck wrote:
> If someone wants to volunteer to write an article about all the delicious
> goodness of 4.5.0, that would be cool, and lwn.net and others would
> be interested in publishing such a thing. But the RMs have enough work
> to do as is, so it shouldn't be up to
t the attached patch momentarily.
--
Mark Mitchell
CodeSourcery
[EMAIL PROTECTED]
(650) 331-3385 x713
2008-10-01 Mark Mitchell <[EMAIL PROTECTED]>
* MAINTAINERS (Blanket Write Privs): Change to Global Reviewers.
Index: MAINTAINERS
=
Eric Botcazou wrote:
>> 2008-10-01 Mark Mitchell <[EMAIL PROTECTED]>
>>
>> * MAINTAINERS (Blanket Write Privs): Change to Global Reviewers.
>
> This is apparently incomplete, see the Non-Algorithmic Maintainers section.
It's a fair question.
I will rai
rid should be the default. There are lots of reasons
LTO isn't going to work for many users for a while (like, for example, a
bug in LTO), and having hybrid object files gives them an easy way to
succeed.
As with any argument about defaults, it depends on what you think is the
"typical"
Richard.
--
Mark Mitchell
CodeSourcery
[EMAIL PROTECTED]
(650) 331-3385 x713
Hello,
I've come across an oddity in C++, involving anonymous unions and
const variables. Neither of the two classes below will compile using
gcc 4.3.0. Is this a bug in gcc or the C++ standard itself ?
class my_class_1
{
union
{
const int x;
const int y;
};
my_class_1() :
On 12/11/2008, James Dennett <[EMAIL PROTECTED]> wrote:
> In a union only one field can be active at one time, hence
> initializing more than one makes no sense
> ...
> However, const items need to be initialized, hence potting two in a
> union makes no sense.
Conceptually there is nothing wrong w
On 12/11/2008, René Bürgel <[EMAIL PROTECTED]> wrote:
> If all members of the union are const, why don't you just make the union
> itself const?
The const for the union seems to be ignored (code below). The
original reason behind the union shenanigans was to provide a
compile-time alias to anothe
ith David.
Code that is known-broken, not known-useful, and which nobody has plans
to fix should just be removed ASAP; it's just a hazard to users.
Thanks,
--
Mark Mitchell
CodeSourcery
[EMAIL PROTECTED]
(650) 331-3385 x713
ptimizing the program away. So, I suggest doing
something like:
volatile char *x = "pr36321.exe";
and passing x to the function, instead of argv[0].
A patch along those lines is pre-approved.
Thanks,
--
Mark Mitchell
CodeSourcery
[EMAIL PROTECTED]
(650) 331-3385 x713
Andreas Schwab wrote:
> Mark Mitchell <[EMAIL PROTECTED]> writes:
>
>> However, I think an even better fix is just to hard-code the string and
>> make it volatile. Presumably, the use of argv[0] here is just to keep
>> the compiler from optimizing the prog
DJ Delorie wrote:
> How about this?
OK.
--
Mark Mitchell
CodeSourcery
[EMAIL PROTECTED]
(650) 331-3385 x713
701 - 800 of 1847 matches
Mail list logo
