Commit e39bbe1b0856 ("memorder: Add example showing store breaking
release-acquire chain") added a couple of code snippets in the
final subsection of Section 15.2.
In 1c builds, this caused the beginning part of Section 15.3 to
appear in the middle of floating code snippets of Section 15.2.
This can be prevented by putting \FloatBarrier in front of Section
15.3, with a (somewhat) wide vertical space left at the end of
Section 15.2.
Note: \FloatBarrier does nothing unless there are some overloaded
float objects. Therefore, 2c and eb builds are not affected.
Signed-off-by: Akira Yokosawa <akiyks@xxxxxxxxx>
---
Hi Paul,
Another option would be to use the "section" option of "placeins"
packages as is done for eb builds. I tried but I got quite a few
sparse-looking pages in other part of 1c builds. So I think adding
a \FloatBarrier here is a reasonable thing to do.
Thanks, Akira
--
memorder/memorder.tex | 2 ++
1 file changed, 2 insertions(+)
diff --git a/memorder/memorder.tex b/memorder/memorder.tex
index 66f75662f26c..f85cfe6ca702 100644
--- a/memorder/memorder.tex
+++ b/memorder/memorder.tex
@@ -2404,6 +2404,8 @@ sea of more complex memory-ordering constraints.
% @@@ Exercises?
% @@@ Hardware details from Appendix?
+\FloatBarrier
+
\section{Compile-Time Consternation}
\label{sec:memorder:Compile-Time Consternation}
%
base-commit: 43d8aa12c84c8b26ffdb8479b4d793cc0159030e
--
2.25.1
