public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: j.vanbemmel@home.nl To: gcc-gnats@gcc.gnu.org Subject: optimization/9086: Missing attachment for #9085 Date: Sat, 28 Dec 2002 13:56:00 -0000 [thread overview] Message-ID: <20021228215240.7043.qmail@sources.redhat.com> (raw) >Number: 9086 >Category: optimization >Synopsis: Missing attachment for #9085 >Confidential: no >Severity: serious >Priority: medium >Responsible: unassigned >State: open >Class: mistaken >Submitter-Id: net >Arrival-Date: Sat Dec 28 13:56:00 PST 2002 >Closed-Date: >Last-Modified: >Originator: j.vanbemmel@home.nl >Release: gcc-3.2 >Organization: >Environment: cygwin >Description: Attachement for bugreport #9085 (I pressed 'submit', forgot to set Submitter-Id, and then it reset my attachement without me noticing it...) To be sure, here's the code attached: /** * Compile with -c -Os -mregparm=2 -fschedule-insns -march=k6 */ class Test { unsigned char track; // 0..79 unsigned char head; // 0..1 unsigned char sector; // 1..18 int e1, e2; public: void f( unsigned p1, unsigned p2, unsigned p3 ); }; void Test::f( unsigned p1, unsigned p2, unsigned lb ) { e1 = p1; e2 = p2; // without this one it will work // convert logical block to physical, this actually depends on drive parameters sector = lb%18 + 1; // 1..18 head = (lb/18)&1; // 0..1 track = lb/36; // 0..79 } >How-To-Repeat: see #9085 >Fix: >Release-Note: >Audit-Trail: >Unformatted: ----gnatsweb-attachment---- Content-Type: application/octet-stream; name="try.cpp" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="try.cpp" LyoqDQogKiBDb21waWxlIHdpdGggLWMgLU9zIC1tcmVncGFybT0yIC1mc2NoZWR1bGUtaW5zbnMg LW1hcmNoPWs2DQogKi8NCg0KY2xhc3MgVGVzdA0Kew0KICAgdW5zaWduZWQgY2hhciB0cmFjazsg ICAvLyAwLi43OQ0KICAgdW5zaWduZWQgY2hhciBoZWFkOyAgICAvLyAwLi4xDQogICB1bnNpZ25l ZCBjaGFyIHNlY3RvcjsgIC8vIDEuLjE4DQoNCiAgIGludCBlMSwgZTI7DQoNCnB1YmxpYzoNCiAg IHZvaWQgZiggdW5zaWduZWQgcDEsIHVuc2lnbmVkIHAyLCB1bnNpZ25lZCBwMyApOw0KfTsNCg0K dm9pZA0KVGVzdDo6ZiggdW5zaWduZWQgcDEsIHVuc2lnbmVkIHAyLCB1bnNpZ25lZCBsYiApDQp7 DQogICBlMSA9IHAxOw0KICAgZTIgPSBwMjsgICAgLy8gd2l0aG91dCB0aGlzIG9uZSBpdCB3aWxs IHdvcmsNCg0KICAgLy8gY29udmVydCBsb2dpY2FsIGJsb2NrIHRvIHBoeXNpY2FsLCB0aGlzIGFj dHVhbGx5IGRlcGVuZHMgb24gZHJpdmUgcGFyYW1ldGVycw0KICAgc2VjdG9yID0gbGIlMTggKyAx OyAgICAvLyAxLi4xOA0KICAgaGVhZCAgID0gKGxiLzE4KSYxOyAgICAvLyAwLi4xDQogICB0cmFj ayAgPSBsYi8zNjsgICAgICAgIC8vIDAuLjc5DQp9DQoNCmdlbmVyYXRlcyBvbiBnY2MgdmVyc2lv biAzLjIgMjAwMjA5MjcgKHByZXJlbGVhc2UpIHVuZGVyIGN5Z3dpbjoNCnNyYy90cnkuY3BwOjI3 OiB1bmFibGUgdG8gZmluZCBhIHJlZ2lzdGVyIHRvIHNwaWxsIGluIGNsYXNzIGBBUkUNCnNyYy90 cnkuY3BwOjI3OiB0aGlzIGlzIHRoZSBpbnNuOg0KKGluc24gMzAgNDkgNTAgKHBhcmFsbGVsWw0K ICAgICAgICAgICAgKHNldCAocmVnOlNJIDQgZXNpIFs2NV0pDQogICAgICAgICAgICAgICAgKHVk aXY6U0kgKHJlZy92OlNJIDYxKQ0KICAgICAgICAgICAgICAgICAgICAocmVnOlNJIDIgZWN4IFs2 Nl0pKSkNCiAgICAgICAgICAgIChzZXQgKHJlZzpTSSAyIGVjeCBbNjRdKQ0KICAgICAgICAgICAg ICAgICh1bW9kOlNJIChyZWcvdjpTSSA2MSkNCiAgICAgICAgICAgICAgICAgICAgKHJlZzpTSSAy IGVjeCBbNjZdKSkpDQogICAgICAgICAgICAoY2xvYmJlciAocmVnOkNDIDE3IGZsYWdzKSkNCiAg ICAgICAgXSApIDI3NyB7dWRpdm1vZHNpNH0gKGluc25fbGlzdCAyOSAoaW5zbl9saXN0IDEwIChu aWwpKSkNCiAgICAoZXhwcl9saXN0OlJFR19ERUFEIChyZWc6U0kgMiBlY3ggWzY2XSkNCiAgICAg ICAgKGV4cHJfbGlzdDpSRUdfVU5VU0VEIChyZWc6Q0MgMTcgZmxhZ3MpDQogICAgICAgICAgICAo bmlsKSkpKQ==
next reply other threads:[~2002-12-28 21:56 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-12-28 13:56 j.vanbemmel [this message] 2002-12-28 14:12 paolo
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=20021228215240.7043.qmail@sources.redhat.com \ --to=j.vanbemmel@home.nl \ --cc=gcc-gnats@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: linkBe 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).