Closed Bug 443454 Opened 16 years ago Closed 15 years ago

Large number of warnings when building with ARM RVCT

Categories

(Tamarin Graveyard :: Tracing Virtual Machine, defect)

Other
Other
defect
Not set
normal

Tracking

(Not tracked)

VERIFIED WONTFIX

People

(Reporter: rob.borcic, Assigned: rob.borcic)

Details

Attachments

(1 file, 2 obsolete files)

Using the ARM RVCT 2.2 compiler to build TT for Symbian, there are several hundred warning messages. This bug will be used to track changes that reduce the warnings to a more manageable number.
The more manageable number should be exactly zero -- and once we get it there, let's convert warnings to errors so they don't crop up.
Example of warning:
Warning:  #830-D: function "MMgc::GCWeakRef::operator new" has no corresponding operator delete (to be called if an exception is thrown during initialization of an allocated object)

This patch adds an empty matching delete operator for FastAllocator, GCObject, GCFinalizedObject, GCFinalizedObjectOptIn, RCObject and GCWeakRef. The extra code is only included if REQUIRE_DELETE_OPERATOR is defined and this flag is currently only defined for Symbian.
Attachment #328004 - Attachment is patch: true
Attachment #328004 - Flags: review?(stejohns)
Attachment #328004 - Flags: review?(stejohns) → review+
The previous patch was included as part of changeset 492:307fb716348c.

This patch further reduces instances of warning #830-D as well as eliminating instances of Warning:  #1165-D: types cannot be declared in anonymous unions.
Attachment #328004 - Attachment is obsolete: true
Attachment #329531 - Flags: review?(stejohns)
The previous patch was missing a change. Sorry about that.
Attachment #329531 - Attachment is obsolete: true
Attachment #329532 - Flags: review?(stejohns)
Attachment #329531 - Flags: review?(stejohns)
Attachment #329532 - Flags: review?(stejohns) → review+
what is the overhead of the delete operators on compilers that don't require them?  put another way what's the cost of making them not-ifdefd?
(In reply to comment #5)
It would depend on the compiler. At best, the compiler would exclude the operator and there would be no overhead. At worst, there would be a small amount of extra code and an extra function call.
pushed as changeset:   514:ecd15452554d
are there more patches coming? else lets mark FIXED
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → WONTFIX
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: