Skip to content

Commit 337a67d

Browse files
committed
Add username to FIXME and TODO
1 parent a583963 commit 337a67d

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

src/builder.rs

+2-2
Original file line numberDiff line numberDiff line change
@@ -1119,7 +1119,7 @@ impl<'a, 'gcc, 'tcx> BuilderMethods<'a, 'tcx> for Builder<'a, 'gcc, 'tcx> {
11191119
modified_destination_type = modified_destination_type.make_volatile();
11201120
}
11211121

1122-
// FIXME: The type checking in `add_assignment` removes only one
1122+
// FIXME(antoyo): The type checking in `add_assignment` removes only one
11231123
// qualifier from each side. So the writes `int → volatile int` and
11241124
// `int → int __attribute__((aligned(1)))` are considered legal but
11251125
// `int → volatile int __attribute__((aligned(1)))` is not. This seems
@@ -1131,7 +1131,7 @@ impl<'a, 'gcc, 'tcx> BuilderMethods<'a, 'tcx> for Builder<'a, 'gcc, 'tcx> {
11311131
self.cx.context.new_bitcast(None, ptr, modified_destination_type.make_pointer());
11321132
let modified_destination = modified_ptr.dereference(None);
11331133
self.llbb().add_assignment(None, modified_destination, val);
1134-
// TODO: handle `MemFlags::NONTEMPORAL`.
1134+
// TODO(antoyo): handle `MemFlags::NONTEMPORAL`.
11351135
// NOTE: dummy value here since it's never used. FIXME(antoyo): API should not return a value here?
11361136
self.cx.context.new_rvalue_zero(self.type_i32())
11371137
}

0 commit comments

Comments
 (0)