public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: tturhan@cs.bilkent.edu.tr
To: tturhan@cs.bilkent.edu.tr
Cc: "GCC Development" <gcc@gcc.gnu.org>
Subject: Re: Modifying the values of Gimple Instruction Operands
Date: Mon, 23 Sep 2013 18:09:00 -0000	[thread overview]
Message-ID: <110d13c4bc1e266db399f64210d0fa32.squirrel@newmail.bilkent.edu.tr> (raw)
In-Reply-To: <a4fdea9c570f333563b759c49bec0e20.squirrel@newmail.bilkent.edu.tr>

Can you guys please help me for variables and pointers ?

Any ideas or pointers will be fine!

Thank you very much in advance.

> Thank you very much Richard,
>
> Very good starter for me but I am actually having the hardest time with
> variables, pointers etc...
>
> I know this may be a lot to ask but,
> If you could help me with this I will very much appreciate it.
>
> Thanks again very much!
> I will be sure to include your name in my paper :)
>
>> On Tue, Sep 3, 2013 at 7:59 PM,  <tturhan@cs.bilkent.edu.tr> wrote:
>>> Sorry forgot to mention, my name is Tuncer.
>>> Again any help would be much appreciated.
>>> I know these maybe simple for some of you if you could lend me a hand,
>>> you
>>> will be doing a great deal of help.
>>> Changed the subject for better understanding,
>>> Thanks again guys :)
>> Something like
>>    oldop = gimple_assign_rhs1 (stmt);
>>    gsi = gsi_for_stmt (stmt);
>>    newop = force_gimple_operand_gsi (&gsi, fold_build2 (BIT_IOR_EXPR,
>> TREE_TYPE (oldop), oldop, build_int_cst (TREE_TYPE (oldop), 1<<3)),
> true, NULL_TREE, true, GSI_CONTINUE_LINKING);
>>    gimple_assign_set_rhs1 (stmt, newop);
>>    update_stmt (stmt);
>>>> Hi,
>>>> I am a student at Bilkent Uni. in Turkey and using GCC as a tool for
> my
>>>> M.S. Thesis which is about Software Fault Tolerance.
>>>> I am stuck, in terms of implementing bit flips in the operands of a
> gimple
>>>> statement.
>>>> I need to inject bit flips to all kinds of operands, constant
> integers,
>>>> floats, variables, pointers etc...
>>>> It is simpler for constants, but I am having a hard time to get the
>>>> value
>>>> of pointers and other variables.
>>>> My objective is to simply change the value of a tree operand, by
> injecting
>>>> a new instruction that changes the value or directly change the
> operand
>>>> to
>>>> a bit flipped value.
>>>> For constant integers I did something like this:
>>>> int valueBefore = TREE_INT_CST_LOW(operands[i]);
>>>> int valueAfter = (valueBefore ^ (1u << 2));
>
>>>>       tree number =
>>>> build_int_cst (integer_type_node, valueAfter);
>>>> I would love it if you can help me and
>>>> may even implement a tool for GCC for error injection purposes. Any
> help would be much appreciated!
>>>> Thank you very much!
>
>
>
>


  reply	other threads:[~2013-09-23 18:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-07 11:53 tturhan
2013-09-23 18:09 ` tturhan [this message]
  -- strict thread matches above, loose matches on Subject: below --
2013-09-01 11:45 Error Injection tturhan
2013-09-03 17:59 ` Modifying the values of Gimple Instruction Operands tturhan
2013-09-04  8:18   ` Richard Biener

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=110d13c4bc1e266db399f64210d0fa32.squirrel@newmail.bilkent.edu.tr \
    --to=tturhan@cs.bilkent.edu.tr \
    --cc=gcc@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).