Should I create a patch and submit it for
official review ?
Cheers
Nick
ns should not be built
outside of
a gcc build tree. Or at least any plugins that require intimate access to gcc's
internal headers.
> I'm still convinced that 99% of all (valid) plugin uses involve only
> introspection or well-defined instrumentation.
I agree, and I would like to see a move towards officially accepting these
plugins
into gcc's ecosystem.
Cheers
Nick
Hi Gerald,
> Thanks for that update, Nick. Surely interesting reading.
> Are you planning another update for March or so? ;-)
Thanks for the ping! I have been intending to write another
update for the last month or so, but I keep on letting it slip. :-(
I will make it my top priority fo
tead. This will mean fewer, but
longer blogs, but hopefully it will still be interesting reading.
Cheers
Nick
lements 128-bit floating point as defined by ISO/IEC/IEEE
60559:2011 (IEEE 754-2008) and ISO/IEC TS 18661-3:2015.
That's it for this time. More in the fall...
Cheers
Nick
configurations, and built and run an x86_64 gdb.
One thing that worries me though, is why hasn't this been done before?
Ie is there a special reason for staying with the old 2.2.7a libtool ?
If not, then does anyone object to my upgrading the gcc, gdb and
binutils mainline sources ?
Cheers
Nick
with more autoconf-fu than me will
have a go one day though.
Cheers
Nick
Hi Guys,
A new version of GLIBC and a whole boatload of new GCC features
means that there is lots to report this time.
---
GLIBC:
Version 2.26 is now out. There are loads of new features and bug
fixes in this release. Some
bug report would be appreciated (mailing list
discussions are useful for raising awareness, but are more likely to
be forgotten over time than bug reports): http://bugs.python.org
Cheers,
Nick.
--
Nick Coghlan | ncogh...@gmail.com | Brisbane, Australia
to include the attribute names in its assembler output.
So - what do people think ? Any objections to this idea ?
Cheers
Nick
*** /dev/null 2011-09-29 08:15:18.023000106 +0100
--- include/binary-file-attributes.h2011-09-29 10:21:09.615305343 +0100
***
*** 0
---
introduction of new ports I do not see any
other changes that re likely to happen.
Cheers
Nick
Standards:
http://savannah.gnu.org/projects/gnustandards
Please try to include one or more assembler test cases to check the
assembly and disassembly of the new instructions.
Cheers
Nick
uld be a bad idea, still
> strictly speaking, gcc is not standards compliant on this one point, and
> rather than change gcc, the defect in the standard could be changed. If
> you don't have anyone participating on the committee right now, you only
> have to convince some one w
l/lib/ -R/usr/local/lib
LD_LIBRARY_PATH=/usr/local/lib:/usr/sfw/lib:/usr/ccs/lib
PATH=/usr/local/bin:/usr/sfw/bin:/usr/ccs/bin:/usr/xpg4/bin:/usr/bin
cmake -D CMAKE_BUILD_TYPE=RELEASE -D CMAKE_INSTALL_PREFIX=/usr/local -D
BUILD_PYTHON_SUPPORT=OFF -D PYTHON_LIBRARY=/usr/local/lib /tmp/OpenCV-2.0.0
I'd really appreciate any help anyone can give, even if it's just to say it's
not a gcc bug!
Many Thanks,
Nick
This email was independently scanned for viruses by McAfee anti-virus software
and none were found
x-*-*
I have a patch to add a "dg-skip-if" line to the pr35318.c file for
these targets. Shall I submit it officially ?
Cheers
Nick
s well), since doubles occupy two
registers.
I can add an xfail for the m32c, but I was wondering if it would
break the importance of the test if the "double" type was changed to
"float" ? This would allow the test to pass for the m32c as well.
Cheers
Nick
ption" which should
satisfy the license scanner.
Cheers
Nick
, mcore, v850 and
xstormy16 backends and they have no problems.
Cheers
Nick
Hi Ian,
Nick, how is gcc --help supposed to work for options which are neither
warnings nor optimizations? For example, -fstack-protector. Is there a
--help option which will display it?
Yes - but only the generic "--help --verbose" rather than a more
qualified version.
My ori
ack-limit-register= Trap if the stack goes past
-fstack-limit-symbol= Trap if the stack goes past symbol
-fstack-protector Use propolice as a stack protection method
-fstack-protector-all Use a stack protection method for every
function
Cheers
Nick
invoke the compiler, assembler and linker.
If that does not work then you could try placing a small script in the
execution search path ahead of the real gcc that echos its arguments and
then calls the real gcc.
Cheers
Nick
* It is essentially a waste of space on hosts that already
have zlib installed.
At the moment I feel that the pros outweigh the cons. What do other
people think ?
Cheers
Nick
Hi H.J.
Right - this decision has been made. We are not going to include
zlib the in the binutils sources.
Thanks for suggesting the idea and working on the patch, but in the
end it was just not a path we wanted to go down.
Cheers
Nick Clifton
}
and
static void
pa_linux_file_start (void)
{
pa_file_start_file (1);
...
}
Anyone know what they're for?
Thanks,
Nick
ps. please CC me as I'm not on the list.
andrake. These
results are with DWARF 2. GCC 4.1.0 with stabs worked as expected
Nick http://www.inet.net.nz/~nickrob
/* -*- compile-command: "cc -g -o simple simple.c"; -*- */
main(int argc, char **argv) {
int i;
i = 1;
}
After starti
e? The above
optimization seems just to save a few bytes unless a program is deeply nested.
Why not reserve it for -O1 and higher?
Nick http://www.inet.net.nz/~nickrob
* intl: Replace contents of intl directory with intl from GCC tree.
Approved for binutils.
Cheers
Nick
Hi Diego,
Jeff's point about our optimizers is also true. Nick, remember that
issue with MIPS optimizations you were discussing with Jeff a few days
ago? I didn't follow most of the details, but it involved ivopts and
sign issues. Could you send a summary?
Sure:
I was lookin
without needing to build a special compiler, that will help
immensely).
Cheers
Nick
Hi Joern,
I have decided to accept employment at ARC International, so effective
11th December 2006, I will step down as an active SH maitainer.
Thank you very much for all the hard work you have out in to maintaining
the SH port (not just in binutils, but in gcc as well).
Cheers
Nick
gt; -std=gnuXX modes?
Meh, even though these macros are a small thing I don't accept the
"things are breaking anyway so let's break even more things" attitude.
This was something that many library authors did during the python 3
transition and that just made the problems orders of magnitude more
horrible.
Cheers,
Nick
, as well as description of
what is wrong with the resulting executable.
Cheers
Nick
xt_real_insn (operands[2]));
=> gcc_assert (GET_CODE (diff_vec) == ADDR_DIFF_VEC);
I am not sure of the best way to fix this, so I am punting to you
guys. :-)
Cheers
Nick
Hi Richard,
I have just noticed that the new -fsched-pressure-algorithm= gcc
command line option is not documented in gcc/doc/invoke.texi. Was
this an oversight ?
Cheers
Nick
e the behaviour
of the scheduler (via the various -fsched-... options) has been very
helpful in getting good benchmark results.
Cheers
Nick
for better instruction scheduling.
Cheers
Nick
rchitecture you are using.
Please contact us at "
Cheers
Nick
know if they're using the open-sourced SOM linker or the 32 bit
> > ELF stuff?
>
> ELF.
yeah, we are using ELF. iirc, binutils is up-to-date wrt NetBSD on PA. The GCC
stuff has never been contributed back. I'll try and fix that.
Nick
NetBSD/hp700 portmaster
using
swap_optab_handler as a replacement function ?
Cheers
Nick
I would be very grateful if
someone could explain what this error really means and maybe point me
towards a solution.
Cheers
Nick
factor of 8
to 12 is too much.
Have you tried using a DWARF compression tool like dwz ?
http://gcc.gnu.org/ml/gcc/2012-04/msg00686.html
Or maybe the --compress-debug-sections option to objcopy ?
Cheers
Nick
testcases 121
# of unsupported tests 172
/work/builds/gcc/current/iq2000-elf/gcc/g++ version 4.3.0 20080123
(experimental) [trunk revision 131756] (GCC)
Cheers
Nick
Hi Joseph,
I have posted some results for the xstormy16-elf target. They are not great
(614 failures) but I do hope that this can target can be removed from the
potential deprecations list.
Cheers
Nick
to know
when they last changed as an indication of how volatile this code might be.
--
Nick http://www.inet.net.nz/~nickrob
;m pretty
> sure (certainly since 3.2).
I was thinking of doing it in Emacs, not Gdb. AFAIK, Gdb can't tell
what compiler created the executable.
> But that would be more appropriate to discuss on the gdb list.
Yes, but are the internals of the STL containers described somewhere,
n the "no deps, predictable, jmp" case like K8 does.
Any comments? (please cc me) Should gcc be using conditional jumps
more often eg. in the case of __builtin_expect())?
Thanks,
Nick
//#define noinline __attribute__((noinline))
#define noinline
#define likely(x) __builtin_expect(!!
> It was before Core2 times, so it might be helping now. But it needs
> updating for backend cost interface as ifcvt is bit inflexible in this.
> I had BRANCH_COST and PREDICTABLE_BRANCH_COST macros.
cmov performance seems to be pretty robust (I was surprised it is so
good), so it definitely seems like the right thing to do by default.
It will be hard to beat, but I hope there is room for some improvement.
Thanks,
Nick
On Wednesday 27 February 2008 03:06, J.C. Pizarro wrote:
> Compiling and executing the code of Nick Piggin at
> http://gcc.gnu.org/ml/gcc/2008-02/msg00601.html
>
> in my old Athlon64 Venice 3200+ 2.0 GHz,
> 3 GiB DDR400, 32-bit kernel, gcc 3.4.6, i got
>
> $ gcc -O3 -falign
e some parts where
__builtin_expect is used quite a lot and noticably helps, and could
help even more if we cut down the use of cmov too. I guess on
architectures with even more predictated instructions it could be
even more useful too.
Thanks,
Nick
On Tuesday 04 March 2008 00:01, Jan Hubicka wrote:
> > On Monday 03 March 2008 22:38, Jan Hubicka wrote:
> > I hope so too. For the kernel we have some parts where
> > __builtin_expect is used quite a lot and noticably helps, and could
> > help even more if we cut down the use of cmov too. I guess
decompression feature,
No it does not.
Cheers
Nick
gen_add_must_preserve_symbol("S"). The LTO engine then
sees it has a weak global function S and it cannot inline those. Put
together
the LTO engine does generate a copy of S, but the linker throws it away
and uses the one from b.o.
-Nick
e lto
interface
matches the Apple linker internal model, so we don't expect and have
not encountered any problems mixing mach-o and llvm bitcode files.
-Nick
On Jun 4, 2008, at 5:00 PM, Ian Lance Taylor wrote:
Nick Kledzik <[EMAIL PROTECTED]> writes:
I don't claim our current implementation is bug free, but the lto
interface
matches the Apple linker internal model, so we don't expect and have
not encountered any problems mixing
On Jun 4, 2008, at 5:39 PM, Ian Lance Taylor wrote:
Nick Kledzik <[EMAIL PROTECTED]> writes:
On Jun 4, 2008, at 5:00 PM, Ian Lance Taylor wrote:
Nick Kledzik <[EMAIL PROTECTED]> writes:
I don't claim our current implementation is bug free, but the lto
interface
matches
d, but must
also be externally visible?
The linker just tells LTO which symbols must remain. The LTO engine
is free to inline anything that would improve codegen, with the
exception
that any weak definition that must remain (preserved) cannot be inlined.
-Nick
t (at http://sourceware.org/bugzilla). Including a *small* test
case will really help.
Cheers
Nick
h them for
the binutils project:
: Since the previous releases were licensed under GPLv2 or later, all
: maintainers need to do is upgrade their backport to GPLv3 or later --
: then they'll be able to incorporate patches that were never released
: under GPLv2.
Cheers
Nick
of all of the sources.
Cheers
Nick
3 (or later)" and have them refer the reader
to the COPYING_v3 file. Files which remain under the GPL version 2 will
then not need to be changed to refer the reader to some file other than
COPYING.
Cheers
Nick
PS. I am also going to be creating a COPYING.LIB_v3 file, although I am
not
accessor function which takes a parameter
indicating the desired field and which returns its current value would
also work.
What do people think ? Is this idea practical, or is there a better
solution ?
Cheers
Nick
uld be particularly helpful to have LLVM folks in
the room, please let me know and I'll help promote it.
See you at the show!
--
Thanks,
~Nick Desaulniers
use the result is a great way to have clang omit the use
from the final program. This has bitten us in the past getting MIPS
support up and running, and one of the MTK gfx drivers.
--
Thanks,
~Nick Desaulniers
't looked up what that is) though maybe
"segment" pseudo qualifiers the kernel defines expand to address space
variable attributes?
Maybe stripping all qualifiers is fine since you can add them back in
if necessary?
const volatile foo;
const nonqual_typeof(foo) bar = foo; // strips off both qualifiers,
re-adds const to bar
--
Thanks,
~Nick Desaulniers
On 9 Mar 2021, Jakub Jelinek via Binutils spake thusly:
> On Tue, Mar 09, 2021 at 11:38:07AM +, Hannes Domani via Dwz wrote:
>> Am Dienstag, 9. März 2021, 10:10:47 MEZ hat Mark Wielaard
>> Folgendes geschrieben:
>>
>> > Hi Allan,
>> >
>> > On Tue, Mar 09, 2021 at 09:06:54AM +0100, Allan Sa
Hello,
This is Nick Vidal from Rocket.Chat
We’ve been part of GSoC for 5 years now, and as a way to celebrate and
give back to the open source community, this year we are reaching out
to other GSoC organizations to provide assistance on setting up
Rocket.Chat to engage with students (pro bono
providing that when configuring
for
just "netbsd" there was a prominentant message in the config log saying
something like:
"netbsd format now treated as ELF based. Use netbsdaout if you want a.out format
files".
(Probably with slightly better wording than that).
Cheers
Nick
Should GCC report shadowing on 'valid' for this code?
Nick
struct S1{bool valid;};
struct S2 : public S1{bool valid;};
struct S3 : public S2{bool valid;};
Ok, sorry. I'll ask it on gcc-help.
Nick
On Wed, Sep 29, 2021 at 1:35 PM, Jonathan Wakely
wrote: On Wed, 29 Sept 2021 at 21:34, Nick Savoiu via Gcc
wrote:
>
> Should GCC report shadowing on 'valid' for this code?
> Nick
>
> struct S1{ bool valid;};
&g
of zlib. I will wait a couple of
days to see if anyone else has any comments or concerns, but if not, then I
will apply the patches myself.
Cheers
Nick
gdb mainline sources with this release.
Whilst it is true that the gcc version of zlib sources had diverged slightly
from
the 1.2.11 release sources, I think that it was just some changes cherry picked
from the developments that went in to 1.2.12. So a simple rebase should be
safe.
Cheers
Nick
the
prune_extra_warnings proc...
Cheers
Nick
program headers
and does not provide separate headers for code and data.
Cheers
Nick
On 27 Jun 2022, Fangrui Song stated:
> I created https://groups.google.com/g/generic-abi/c/satyPkuMisk ("Add new
> ch_type value: ELFCOMPRESS_ZSTD") after I saw that on LLVM side, Cole Kissane
> proposes that we add Zstandard as new compression method (mainly for .debug*
> sections, but also for s
both compilers).
This sounds like an opportunity to add a couple of new GNU object
attributes:
.gnu_attribute Tag_gnu_destructor_count,
.gnu_attribute Tag_gnu_tld_count,
Which would then translate into a GNU object attribute notes in the
object file.
Cheers
Nick
ntly for
nvptx?
Nope, none at all.
Harmonizing the effect of the -v option sounds like a good idea to me.
Cheers
Nick
ed
I looked into providing a file name and line number with the error
message, but this would involve reworking a lot of the assembler's
internal expression parser.
Cheers
Nick
expressions that cannot
be resolved this way. That is why the error message refers to
"converted into relocations" rather than just "converted into a
relocation".
Cheers
Nick
it is not clear which tool is the source of the problem, then I would
suggest choosing the binutils first. If it turns out that specific issue
is actually caused by a problem in gcc, the bug report can always be moved
later on.
Cheers
Nick
addressing. I will try to make time for them in the next
few weeks.
If you do have any suggestions for fixes to any of these problems, please do
feel free to add them to the relevant bug reports.
Cheers
Nick
en link your program.
Of course without those startup files you may not be able to run
your code, but I assume that that does not matter to you.
Cheers
Nick
101 - 181 of 181 matches
Mail list logo
