Ik zie ook wat leuke dingen in de release notes:
* MIPS targets now support the -fstack-protector option.
Uit de handleiding:
-fstack-protector
Emit extra code to check for buffer overflows, such as stack smashing
attacks.
This is done by adding a guard variable to functions with vulnerable
obje
Tim,
Nice. It reads: "3.2.3. Intel syntax - Good news are that starting from
binutils 2.10 release, GAS supports Intel syntax too. It can be
triggered with .intel_syntax directive. Unfortunately this mode is not
documented (yet?) in the official binutils manual, so if you want to use
it, try to e
On 08/09/10 08:42, John Regehr wrote:
On Sat, 7 Aug 2010, Florian Weimer wrote:
I wonder if we should give up and make -fwrapv the default.
My sense is that there are not that many of these integer bugs, and
probably all of them are simple to fix. Best to just fix them and then
run a tool like
On Mon, 9 Aug 2010, John Regehr wrote:
> On Sat, 7 Aug 2010, Florian Weimer wrote:
> > I wonder if we should give up and make -fwrapv the default.
>
> My sense is that there are not that many of these integer bugs, and probably
> all of them are simple to fix. Best to just fix them and then run
Hi Jeff,
I'm looking at the remaining text peepholes (define_peephole instead
of define_peephole2) and I have a few questions about mn10300, that
you are a maintainer of.
The first peephole is this:
;; Try to combine consecutive updates of the stack pointer (or any
;; other register for that mat
Dear all,
I am trying to build cross compiler for xc16x. I built successfully
binutils 2.18; gcc 4.0 and newlib 1.18. Everything is fine when
compiling a simple C file without any library call. It is also fine
when making a simple call to printf like printf("Hello world").
However, i got error mes
Hi,
I am thinking (as I am not familiar with IRA) to the following
alternative to your solution:
I set to zero all CALL_USED_REGISTERS (except the fixed regs), and
then in the expand_call I set CALL_INSN_FUNCTION_USAGE to the list of
clobbered registers (given by attribute attached to a function
Hello,
Forgive me if I overlooked it, but I can't find in the manuals what
the semantics would be of the following define_expand, from avr.md:
(define_expand "cbranchsi4"
[(parallel [(set (cc0)
(compare (match_operand:SI 1 "register_operand" "")
(m
Steven Bosscher wrote:
> Forgive me if I overlooked it, but I can't find in the manuals what
> the semantics would be of the following define_expand, from avr.md:
>
> (define_expand "cbranchsi4"
> [(parallel [(set (cc0)
>(compare (match_operand:SI 1 "register_operand" "")
>
On 08/09/2010 01:39 PM, Ulrich Weigand wrote:
(define_expand "cbranchsi4"
[(parallel [(set (cc0)
(compare (match_operand:SI 1 "register_operand" "")
(match_operand:SI 2 "nonmemory_operand" "")))
(clobber (match_scratch:QI 4 ""))])
On Mon, Aug 9, 2010 at 7:39 PM, Ulrich Weigand wrote:
> That's incorrect; the second pattern of the PARALLEL is just a CLOBBER.
Ah, parse error :-)
Thanks for your help!
Ciao!
Steven
On 08/09/2010 06:28 AM, Steven Bosscher wrote:
> I would like to convert these remaining define_peepholes to
> define_peephole2s instead. However, I can't find a define_insn that
> produces the bcs or bcc instructions. Could use a little help figuring
> out what insn I should generate in the peepho
On 08/09/2010 07:20 AM, Claudiu Zissulescu wrote:
> I set to zero all CALL_USED_REGISTERS (except the fixed regs), and
> then in the expand_call I set CALL_INSN_FUNCTION_USAGE to the list of
> clobbered registers (given by attribute attached to a function
> declaration). Then, I should be able to
Hello,
It seems that there once was support for builtin functions defined by
a front end. This is still a useful idea (see e.g. PR24777) but it
looks like there are no frontend built-in functions anymore. At least,
a grep for BUILT_IN_FRONTEND gives no meaningful results. There's a
hint that it ma
On 9 August 2010 08:08, Rick C. Hodgin wrote:
> Tim,
>
> Nice. It reads: "3.2.3. Intel syntax - Good news are that starting from
> binutils 2.10 release, GAS supports Intel syntax too. It can be
> triggered with .intel_syntax directive. Unfortunately this mode is not
> documented (yet?) in the off
Hi Tom,
Assertions in libcpp have been deprecated since r135264:
2008-05-13 Tom Tromey
PR preprocessor/22168:
* expr.c (eval_token): Warn for use of assertions.
Can this feature be removed for GCC 4.6?
Ciao!
Steven
16 matches
Mail list logo
