public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: xunxun <xunxun1982@gmail.com>
To: jojelino <jojelino@gmail.com>
Cc: gcc@gcc.gnu.org, qemu-devel@nongnu.org,
	 Kai Tietz <ktietz70@googlemail.com>
Subject: Re: gcc auto-omit-frame-pointer vs msvc longjmp
Date: Sat, 22 Oct 2011 12:30:00 -0000	[thread overview]
Message-ID: <4EA250E0.3080808@gmail.com> (raw)
In-Reply-To: <j7sgfi$i66$1@dough.gmane.org>

[-- Attachment #1: Type: text/plain, Size: 535 bytes --]

Hi, all

     It seems that gcc's auto-omit-frame-pointer has other problems.

     The example is from mingw bug tracker: 
http://sourceforge.net/tracker/?func=detail&aid=3426555&group_id=2435&atid=102435

     g++ -O3 main.cpp       running will crash.
     g++ -O2 main.cpp       running no crash.
     g++ -O3 -fno-omit-frame-pointer    running no crash.

     I don't know in the end which optimize option defaultly contains 
this switch "-fomit-frame-pointer" on i686-pc-mingw32 or x86_64-w64-mingw32?

-- 
Best Regards,
xunxun


[-- Attachment #2: main.cpp --]
[-- Type: text/plain, Size: 750 bytes --]

#include <vector>

typedef void (*Func)(char*);

bool lie = false;
Func dummy = 0;

void moveToWindowsRecycler(const std::vector<int>& filesToDelete = std::vector<int>())  //throw FileError
{
    if (!lie)
        throw 1;

    char errorMessage[20000];

    Func fun = lie ?  dummy : 0;
    fun(errorMessage);

    std::vector<int> fileNames;

    for (std::vector<int>::const_iterator iter = filesToDelete.begin(); iter != filesToDelete.end(); ++iter)
        fileNames.push_back(*iter);
}

void wgfdfsdgfsdgfsdg()  //throw FileError
{
    ::moveToWindowsRecycler();  //throw FileError
}

int main()
{
    try
    {
        moveToWindowsRecycler()  ;//throw FileError
    }
    catch (...) {}

    return 0;
}

  reply	other threads:[~2011-10-22  5:13 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4E9BB180.6080506@mc.net>
     [not found] ` <4E9C0497.2000605@siriusit.co.uk>
     [not found]   ` <4E9C3703.3040109@mc.net>
2011-10-17 21:20     ` Richard Henderson
2011-10-17 21:32       ` [Qemu-devel] " Blue Swirl
2011-10-17 22:23         ` Richard Henderson
2011-10-17 22:56       ` Bob Breuer
2011-10-18  2:06         ` Kai Tietz
2011-10-18  4:20           ` Bob Breuer
2011-10-18  4:22             ` Kai Tietz
2011-10-20  3:26               ` Bob Breuer
2011-10-20  4:18                 ` Richard Henderson
2011-10-20  6:08                 ` xunxun
2011-10-20 15:01                   ` Kai Tietz
2011-10-20 17:12                     ` Kai Tietz
2011-10-21 22:47                       ` jojelino
2011-10-22 12:30                         ` xunxun [this message]
2011-10-22 13:18                           ` xunxun
2011-10-22 14:21                             ` Kai Tietz
2011-10-22 22:59                       ` asmwarrior
2011-10-24 20:05                       ` [Qemu-devel] " Bob Breuer
2011-10-24 23:25                         ` Kai Tietz
2011-10-25 17:00                           ` Bob Breuer
2011-10-20 14:16                 ` jojelino

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=4EA250E0.3080808@gmail.com \
    --to=xunxun1982@gmail.com \
    --cc=gcc@gcc.gnu.org \
    --cc=jojelino@gmail.com \
    --cc=ktietz70@googlemail.com \
    --cc=qemu-devel@nongnu.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).