mirror of
https://github.com/c64scene-ar/llvm-6502.git
synced 2026-04-26 12:20:42 +00:00
Spell `necessary' correctly.
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@7944 91177308-0d34-0410-b5e6-96231b3b80d8
This commit is contained in:
@@ -150,7 +150,7 @@ needed...
|
||||
Conditional move is effectly a special case of a predicated
|
||||
instruction... and I think that all predicated instructions can possibly
|
||||
be implemented later in LLVM. It would significantly change things, and
|
||||
it doesn't seem to be very neccesary right now. It would seem to
|
||||
it doesn't seem to be very necessary right now. It would seem to
|
||||
complicate flow control analysis a LOT in the virtual machine. I would
|
||||
tend to prefer that a predicated architecture like IA64 convert from a
|
||||
"basic block" representation to a predicated rep as part of it's dynamic
|
||||
|
||||
@@ -144,7 +144,7 @@ least*:
|
||||
2. A pointer to the dtor for the contained object
|
||||
3. The contained object itself
|
||||
|
||||
Note that it is neccesary to maintain #1 & #2 in the exception object itself
|
||||
Note that it is necessary to maintain #1 & #2 in the exception object itself
|
||||
because objects without virtual function tables may be thrown (as in this
|
||||
example). Assuming this, TryHandler would look something like this:
|
||||
|
||||
|
||||
@@ -43,7 +43,7 @@ Changes:
|
||||
|
||||
which is much more natural and what users expect.
|
||||
|
||||
* Simplification of #include's: Before, it was neccesary for a .cpp file to
|
||||
* Simplification of #include's: Before, it was necessary for a .cpp file to
|
||||
include every .h file that it used. Now things are batched a little bit more
|
||||
to make it easier to use. Specifically, the include graph now includes these
|
||||
edges:
|
||||
|
||||
Reference in New Issue
Block a user